Yes. Duplicator Pro writes package history, schedules, and storage destination configuration to WordPress options and its own tables. SleekAI's data sources map those rows into named variables the chatbot uses at request time. The Wizard handles the mapping in a few minutes and supports including only the fields you want the model to see.

Not unless you configure it that way. Display conditions on user role, capability, logged-in state, and URL pattern keep the migration bot scoped to administrators inside wp-admin. Any public chatbot you run on the same site is a separate bot under multibot, with its own data sources and no access to Duplicator rows.

The bot can read whatever Duplicator writes to your database, so the Lite plugin's manual package history is visible. Pro-only fields like scheduled backups, cloud storage destinations, and Pro-specific retention configuration only exist when Duplicator Pro is installed and active. The core flow of querying last package and size works for both.

By default SleekAI is read-only against Duplicator data. It explains state and points at the right button. If you want a chat-initiated build, you can wire a custom PHP callback into a SleekAI tool, but most teams keep package builds and installer runs inside the Duplicator UI where confirmations are explicit.

Yes. Conversation logging is on by default per chatbot, with user messages, assistant replies, model name, token usage, and the page URL stored inside WordPress. For a migration bot, that audit trail matters: when a package the bot referenced is later used for a restore, the trace exists.

It can describe the latest package and where it lives, but the actual installer.php run, search-replace, and DNS cutover happen outside the bot. Most agencies have the bot summarise pre-flight state, then follow Duplicator's installer for the move itself, which is the safer pattern for any URL rewrite.

A fast model is fine for routine reads like last-package timestamps and schedule names. For longer prompts that compare two packages or explain a build error, a stronger model from OpenAI, Anthropic, Google, or OpenRouter gives better synthesis. SleekAI lets you pick the model per chatbot, so cost matches workload.

Each SleekAI install runs its own chatbots with its own data sources, so configuration is per site. You can export the chatbot config and re-point the data sources on a new site, which is handy when you want the same migration-help bot across a portfolio of Duplicator Pro client sites.