Skip to main content
Theme

Reference

Statuses

Every status and mark the tool shows, in the color it shows it, and what it means.

The colors

Each color means the same thing wherever it appears: on the migrations list, at the top of a migration, in the checks and in the emails.

ColorMeans
BlueWorking. Nothing for you to do: it carries on by itself and emails you when it needs you. If it is not paused and gets no further for 30 minutes, the person who started it and Insites are emailed, once.
GreenDone, and it went well.
AmberLook at it, or decide something. Nothing has gone wrong that cannot be put right.
RedSomething went wrong, or cannot be copied as it is. The page says what, and what to do.
GrayA plain fact, or waiting for you. Nothing is wrong.

A migration's status

Shown on the migrations list and at the top of every migration. The last column is the choice in the migrations list's Status filter that shows it.

Beside the status, each row of the migrations list says who started the migration, by the email they signed in with (You for your own, and Not recorded for an older migration that did not keep it), and where it is in the same words as the migration's own page: "Stage 4 of 7 · Plan" and "Step 1 of 5". A small bar shows how far through the seven stages it is, and while it loads, the bar moves with the load.

The migrations list

Each row also says which Environment the new instance is: Production or Staging, the only two an Insites instance has. The tool reads it from the instance's address: one ending staging-insites.io is Staging, and one ending prod01-insites.io is Production. When the address is the site's own domain, it says Not known rather than guess. The same word is shown beside the new instance's address at the top of the migration.

Under the status, a migration that is waiting for a person says how many things: Needs you: 4. It adds up three kinds, and pointing at it says which: decisions on a plan waiting for approval (as the plan's Needs you counts them, and a night of the nightly sync that stopped for you), the Things that need you on Verify that are not yet dealt with, and the jobs on the To do list not yet done. A migration that needs nothing shows no count. A closed migration, and a run that a later sync has replaced, show none either: open the newest run of it instead.

Above the list, choose what to show. Each filter narrows the one before, and they all apply together:

  • Search: part of the old site's or the new instance's address, or a migration id. A migration is found by the address of any sync that followed it, too.
  • Environment: Production or Staging. A migration whose environment is Not known shows only under All.
  • Old site platform: each platform the tool can migrate from, such as Insites v5, Webflow, Squarespace or Siteglide, and any other a migration in your account came from.
  • Stage: the stage the migration's next step is in, from Source to Launch.
  • Status: Running, Needs you, Verified, Verified with problems, Closed, or Failed or stopped. Each migration is in exactly one, from its newest run, as the table below says.
  • Started by: the person who started the migration.

The list shows 25 migrations a page, newest first, and says which: "Showing 26 to 50 of 132". Press Next and Previous to move between pages. The filters and the page are in the page's address, so you can send a filtered view to someone in the same account and they see the same list. Nobody outside the account sees any of it. The tool also remembers your last choice in this browser and uses it the next time you open the list. Clear the filters shows every migration again.

StatusWhat it meansWhat to doFilter
Reading the sourceIt is reading everything the source instance holds: tables and rows, people, code, files and settings. The source is never changed.Nothing. The page shows how far it has got.Running
PlanningIt is working out what a load would do: what is copied, what changes on the way, what the destination already has, and anything that needs a decision. Nothing is written.Nothing.Running
Needs a decisionThe plan is ready, and something must be decided before anything can load: a secret in the data, code v6 will not accept, a form whose table stays behind.Open the plan and decide each one. Most are one press.Needs you
Nightly sync is waiting for youLast night's sync stopped before copying anything. Either someone changed rows on the new site after they were copied, and copying again would write over those changes, or another migration was working on the new site. Nothing was written.Open it. Load lists each changed table: choose Keep the new site's rows or Take the old site's rows for each, then press Carry on. MoreNeeds you
Waiting for youThe plan is ready and nothing blocks it. Nothing has been written yet.Read the plan, then type its code to start the load.Needs you
Dry run in progressIt is working out exactly what a load would write, update and give new ids, against the real destination, without writing anything.Nothing.Running
Dry run doneThe dry run finished and the page shows what a load would do. Nothing was written.Run it for real, change the transform, or close the migration.Needs you
LoadingIt is writing to the destination in steps: rows with their ids and dates, people, code, files and constants. Every write is recorded, so it can be rolled back.Nothing. You can close the page: it emails you when the load finishes, and again when the checks finish.Running
VerifyingThe load finished and the checks are running: rows, people, files, code, settings and pages are compared with the source. You were emailed when the load finished.Nothing. It emails you the verdict when the checks finish.Running
VerifiedEvery check passed: the destination holds what the source holds.Work through the To do list, then the cutover.Verified
Verified, with problemsThe load finished and at least one check failed. The result shows each difference.Copy again what differs, or accept it with a reason, then check again.Verified with problems
PausedAn instance stopped answering while it worked, or answered with a gateway error (such as a 502, or a 520 to 530 from the network in front of it). It waits and tries again by itself, up to six times over about two hours, and carries on from where it stopped. Nothing is lost. A try you ask for with Try again now does not count toward the six. When a request is too slow for the instance, the tool asks again with a smaller one rather than repeating the same request. When Insites briefly cannot check a key and asks the tool to wait, the tool waits the time Insites gives, up to a minute, and sends the same request again before it pauses: Insites did nothing with the first one. If it still cannot get through, the run fails, and you can carry on from there later.Nothing, or press Try again now. If it keeps pausing, the instance may be down.Running
Stopping...Someone pressed Stop. The call to the destination in hand finishes first, usually within half a minute, then it stops.Wait a moment.Running
StoppedSomeone pressed Stop. Nothing more runs. Anything it had written stays on the destination.Carry on from where it stopped, or roll back what it wrote.Failed or stopped
FailedIt hit a problem it could not get past by itself, and stopped. Every page of the migration says what went wrong in plain words, with the raw message under Technical detail. The person who started it, and Insites, are emailed.Fix what the message names, then press Carry on from where it failed: it goes back to the step that failed and keeps what it already did. When a saved key is the problem, the page offers Give the migration a new key first. Or change the transform and plan again, roll back what it wrote, or start a new migration.Failed or stopped
Rolling backIt is removing everything the load wrote and putting back everything it changed, from the record it kept.Nothing.Running
ClosedSomeone closed the migration on the Close step, which removed its keys and its copy of the old site. Every run of the same migration reads Closed too, because they shared those keys. It read Finished before October 17, 2026. A migration planned again from it has keys of its own, so it stays open. Its report and decisions stay.Nothing: it is a record. To migrate the site again, start a new migration.Closed
DeletedAn owner deleted the migration, which closed it and took it off the list. Only Insites staff see a deleted migration, with who deleted it and when.Nothing: it is a record.Closed
Rolled backThe destination is as it was before the load. Tables the load created are removed, and columns it added to a table that was already there stay, empty.Plan it again when you are ready, or close the migration.Needs you

Check results

Each check the verify step runs. The checks says what each one compares.

MarkWhat it means
PassedThe check found no difference between the source and the destination.
NoteAn advisory check found a difference worth a look. Advisory checks (every page answers the same, every page looks the same) never decide the verdict, because a page can differ for an honest reason, such as today's date.
FailedThe destination does not hold what the source holds. The migration reads Verified, with problems until it is copied again or accepted.
Not checkedThe check could not read what it compares, so it has no verdict: not a pass, and not a failure. The old site gave no answer, refused the tool, or the new site could not be read, for most of what the check looks at, and nothing it did read differs. It does not count against the migration and is not offered Copy again. It says what could not be read and why, under Worth a look, with Check again.

Earlier checks

MarkWhat it means
PassedEvery check passed that time.
ProblemsAt least one check failed that time. The entry names which.
Could not runThe check could not run, usually because a key stopped working. The result before it stands.

The 14-day watch

MarkWhat it means
PassedEvery page answered as it did at verification, and the destination logged nothing new.
Worth a lookA page answered differently, or the destination logged errors. The entry lists them. A page that used to ask visitors to sign in and now opens without it is listed as such.

Checks on the new site

On each check Launch runs on the new site around the cutover, such as Search engines can find it, under Checks on the new site on the Before cutover and After cutover steps.

MarkWhat it means
PassedThe check found nothing wrong at the address it looked at.
FailedThe check found a problem. Each one names the address it is about.
For informationWorth knowing, and not a fault. Before the domain moves, an instance address kept out of search engines is expected.
Not checked yetThe check has not run on this migration. Press Check again.

Errors the new site logged

On each kind of error the LOGS check lists under Worth a look. The tool compares each one with the old site's own log, and says whose it is.

MarkWhat it means
Yours to fixThe error is in the site's own code or setup, and the old site's log does not have it. Fix it on the new instance before you switch the domain: each one says how.
In a To do jobA To do job not yet ticked sets it right, and the error opens that job. A form or page that checks reCAPTCHA is the common one: the new instance has no reCAPTCHA keys until the job Set up the spam check (reCAPTCHA) on the new site's forms is done, and keys are never copied in a migration. The check accepts it until the job is ticked. If it is still logged after that, it is yours to fix again.
The old site has this tooThe old site's log has the same error, or the old site has the same fault, so the migration did not cause it. A form on a page that is searchable on the old site too is one: the instance logs it each time the page is saved, and the old site's log keeps only its latest entries. Nothing to do before cutover. The check accepts it.
Also fails on the old siteThe tool asked the old site for the same page, once, and that page fails there too: it answers with a server error, or shows an error in the page. So the migration did not cause it, and the check accepts it. These come last. When no page, partial or layout in the site's code links to the page, or nothing shows the partial, it says so: such a page may be code the site no longer uses. When the old site could not be read, the error stays yours and says Not checked on the old site, with why.
Fixed sinceEvery time the error was logged came before the tool last copied its page's code, with Copy this one again, Copy all again, Copy the old site's version again or the load, and this check opened that page on the new site and it answered with no error. It shows when the error was logged and which copy came after, and it is not counted. If the error is logged again after the copy, it is counted again.
Insites module: not yoursThe error is in code a module Insites provides, not the site's code, and the migration did not write it. Nothing for you to fix, and the check accepts it. If it keeps appearing, send it to [email protected]. A line from the new instance's cache starting up, such as "Redis is loading the dataset in memory", is labeled Insites cache: not yours in the log and in the To do list. It passes by itself in a moment, the check accepts it with that reason, and it makes no To do job.

When the old site's log cannot be read, the tool says so on each error and never marks one as the old site's too.

Connecting a source

On each permission a key was checked for, when the source takes a key with permissions, such as a Webflow site API token.

MarkWhat it means
Can readThe key has this permission, and the tool read with it.
MissingThe migration needs this permission and the key does not have it. Make a new key with it set to Read-only.
Not givenA recommended permission the key does not have. The migration goes ahead without what it reads, and the line under the mark says what that is.

What an instance holds

On each module and setting in What it holds. What is copied says what each module carries.

MarkWhat it means
CopiedAfter the load: copied to the destination and checked afterwards.
Will copyBefore the load: this will be copied to the destination.
CopyingThe load is copying it now.
Created emptyA table of yours that holds no rows. It is created on the destination with its fields, so the site can write to it after the migration. Every table the instance defines is listed, empty ones included, so the count matches the instance's own admin.
ReplacedThe destination has its own, and the source's would be wrong there: its own API keys, password reset links, each module's own code.
You do thisNo API can create it, so you do it, and it goes on the To do list, for example an integration's key. A module card counts them: 2 for you to do.
Stays on the old siteA log of what the old instance did, such as every email it sent. Counted in the report and not copied: the new instance keeps its own.
NoneThe instance has none of this.

On the Transform steps

Each Transform step lists one kind of thing the site holds, and says what happens to each one. Nothing on the old site is changed or deleted: everything is copied.

MarkMeans
CopiedAfter the load: copied to the new site and checked afterwards.
Will copyBefore the load: this will be copied to the new site.
CopyingThe load is copying it now.
RebuiltMade again on Insites from what the old site shows, such as a website's pages, and checked afterwards.
Recreated in InsitesA form, made again on the new site with the database it saves to.
You do thisNot copied by the tool: you do it on the new site, and it is on the To do list.
Not copiedLeft on the old site, with its reason beside it. The report counts it with that reason.
Will skipBefore the load: this will not be copied, and its reason is beside it.
SkippingThe load is running and leaves this behind.
Stays on the old siteA record the old site keeps for itself, such as its sent email log or its data exports. Insites cannot load it into a new instance; download what you need from the old site's admin before you switch it off.
Not chosen yetSettings and keys you pick one by one, with none picked, so none will be copied. The link beside it opens the plan, What the load carries, where you choose them. With some picked, the mark says how many, such as Will copy 3 of 9.
NoneThe site has none of this.
Coming soonThe tool cannot read this kind from this platform yet. The step says what happens to it until then.

On the plan

Tables

MarkWhat it means
CopiedAfter the load: the table's rows loaded, with their ids and dates.
Will copyBefore the load: this will be copied to the destination, with its ids and dates.
CopyingThe load is copying it now.
Not copiedThe table is not copied, because you left it behind or the transform does (logs and history). Its rows are still counted, so the coverage check accounts for every one.
Will skipBefore the load: this will not be copied, and its reason is beside it.
SkippingThe load is running and leaves this behind.

The plan's table list also has a Private files column: each upload column whose files the source keeps private. Those files are read through signed addresses and written private on the destination, and the FILES check proves they still need a signature to open.

Module versions

Every Insites instance has every Insites module, so the plan compares versions only. Fixes lists a module only when the new instance runs an older version of it than the old one.

MarkWhat it means
MatchesThe new instance runs the same version of the module as the old one, or a newer one.
DiffersThe new instance runs an older version of the module than the old one. Update it in Insites Console before the load.

Code v6 will not take as it is

Each mark says what the file needs from you.

MarkWhat it means
Fix to choosev6 refuses the file as it is, and the tool can change it so v6 takes it. Tick Apply this fix to copy it with the change shown. Leave it and the file is not copied.
Will applyThe fix loses nothing, so it is on by default and saves by itself. The file will be copied with the change. Switch it off to leave the file behind.
Not appliedYou switched the fix off, so the file will not be copied. Switch it on to copy it with the change.
Stays behindv6 refuses the file as it is and the tool has no fix for it. Fix it on the old site and run a final sync, or leave it.
To do after the loadNothing to do now: the file is copied. Something about it needs a person on the new instance afterwards, such as a policy's HTTP status or a layout the new instance does not have, and it is a job on the To do list.

Links to the old instance

A web address (URL) in the old site's code or data that points at the old instance. The Insites glossary keeps the word "address" for a CRM postal address, so the tool calls these links and URLs.

MarkWhat it means
Custom domain: no changeThe site's own domain, such as www.example.com. It moves to the new instance at cutover, so links to it keep working. Nothing to do.
Instance URLThe old instance's own URL. It stops working when the old instance is deleted. Tick Replace to point it at the new instance's URL.
File storage URLWhere the old instance keeps uploaded files. It stops working when the old instance is deleted. Tick Replace to point it at the new instance's file storage.

While you work on it

MarkWhat it means
ResolvedSomething an earlier plan asked you to decide, that your changes settled.
Changed, not saved yetYou changed the transform and have not saved it. Nothing uses the change until you save and plan again.

An agency's people

MarkWhat it means
SentThe invitation email went, at the time shown.
Could not sendThe invitation email could not be sent. The reason is beside it: an owner can send it again.
Not sentNo invitation has been emailed to this person yet. An owner can send one.