How-to
Ask about a migration
Once a migration has a plan, you can ask AI about it in plain words: how the rows were copied, what happened to a file, whether a check took something into account. You can also ask how to do something in the tool: how to change the plan, who fixes an error, where to get the moved code. It answers from this migration’s own record and from these docs, and links to the steps and the pages it read so you can check for yourself.
- Open the migration on the Plan step or any step after it, and click Ask about this migration at the top.
- Type your question, or pick one of the examples, and press Ask. Name the thing you mean where you can: a table, a file, a check, a job on the To do list.
- Read the answer, then open the links under it. Each one goes to the step that shows that part of the record.
- If the page moves while you type, such as when you press Back, the cursor stays in the box and nothing you typed is lost.
- Ask a follow-up in the same box. The panel keeps your last few questions, so you can say “and the people?” without starting again.
What it reads
This migration’s record: the plan and what it carries, the load, every check and what it found, the decisions and why they were made, the transform settings, the To do list and the reports. Never another migration’s. For a big site it reads the parts your question names, so name the table or the file when you ask about one.
With every question it also reads:
- These docs, the sections that match your question. A link to a docs page opens in a new tab, so the migration stays open.
- The screens and their buttons, by the words on each button, so it can say which button to press and on which step.
- Where to move a run to another instance. Move again to another instance is on Launch, on Close, and on the Where to go from here card of a load that was rolled back. Run again with the latest fixes is on Verify, Result. Ask for either and it names the button and the step.
- Who fixes each kind of problem, in the same words as the migration’s own message and email: you, Insites, or nobody yet. When something goes wrong.
- Who is asking: your name, your address and your role in this account, and who its owners are. It answers you as you, and never tells you to ask yourself.
- Where the migration is now, read at the moment you ask: its status, whether the tool is working on it, its last check and what it needs next. An answer kept in the panel describes the migration as it was when it was asked.
It is never sent a key, a token, a password or its hash, a credential, a constant’s value, a redacted field’s value, or a row of the site’s data. Email addresses of the site’s people are hidden too; your own team’s stay readable. What AI is sent.
Who can ask, and how often
- Anyone who can see the migration can ask, viewers included. Asking changes nothing on the migration.
- The last 20 questions and answers are kept with the migration, so the next person who opens the panel sees them.
- Each person can ask AI about one migration 20 times an hour, questions and Find out more together. The panel says how many are left.
- A migration can reach its AI limit. The panel then says so and stops answering. Ask Insites support to raise it.
Find out more on a To do job
Each job on the To do step has a Find out more button. It explains, for someone who is not technical, what to do, why it matters for this site, and what goes wrong if it is skipped. It does not change the job: the job’s own steps are what to follow. The explanation is kept on the job, so it is only asked for once.
Suggest a fix on a check
On Verify, Things that need you, each problem has a Suggest a fix button. AI reads what that check found and says what is wrong, why, and the change, and offers one of the tool’s own buttons when one fits. Suggest a fix.