It sees the metadata around them, including filename, size, and timestamp, by reading WordPress options and the contents of the wp-content/ai1wm-backups folder. It does not crack open the .wpress archive itself. For most admin questions, the metadata layer is what matters: which file is current, how big it is, and which options produced it.

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 overlap.

Yes. The free version of All-in-One WP Migration writes the same kind of metadata to WordPress that SleekAI can read. Premium and storage-extension data, like remote destination configuration, also persists locally and can be mapped into the prompt. The bot reads whatever is stored in the database and the backup folder.

By default SleekAI is read-only against migration data. It surfaces state and explains options. If you want a chat-initiated export, you can wire a custom PHP callback into a SleekAI tool, but most teams keep export and import inside the All-in-One WP Migration UI where the upload limit and find-and-replace dialogs 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 an import goes wrong, the team can trace which export file the bot referenced and why.

It can quote the current file size and explain that the destination server's upload_max_filesize and post_max_size need to cover that number. The actual php.ini or .user.ini edit happens outside the bot, but the chat exchange documents the size the receiving server has to handle.

A fast model is fine for routine reads like last-export timestamps and option flags. For longer prompts that explain a stuck import or compare two export files, a stronger model from OpenAI, Anthropic, Google, or OpenRouter gives better synthesis. SleekAI lets you pick the model per chatbot.

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 useful when the same migration-help bot is wanted across multiple All-in-One WP Migration client installs.