Skip to main content
Theme

How-to

Move a staging migration to production

When you have moved a site to a staging instance and checked it there, move it again to production without making every plan decision a second time. The tool makes a new migration from the same old site to the production instance, with every decision from the staging move, and starts it as a dry run.

How to move it again

  1. Create the production instance in Insites Console, and take its access token from its CLI tab, made with the Developer role. See Get the key for each instance.
  2. Open the staging migration. It must have loaded. It can be checked, rolled back or closed.
  3. Press Move again to another instance. It is on the Close step of Launch, and on the card under Where to go from here of a load that was rolled back.
  4. Give the production instance's address and its access token. If the staging migration is closed, or no longer holds a key for the old site, give the old site's key too.
  5. Press Start the dry run. The tool tests the new instance, reads the old site again and builds a new plan. It opens as soon as it starts.
  6. Read the plan. Its first page says what came from the staging move, what no longer applies and what is new on the old site. Decide what is new, then look through the rest of the plan as for any move.
  7. When the plan is right, press Run it for real and confirm it with the plan code. Nothing is written to production before that.

Moving again needs the operator or owner role. See Roles.

What is carried

Every decision about the site, matched by what it names: a database, a field, a row, a code file, a form, a constant.

  • Databases: the tables left behind or created from the data, the fields renamed or dropped, the values hidden, the flagged columns kept, the rows left behind and the values fixed, and each table's names and tooltips.
  • Pages and code: the code fixes and rewrites, the code files left behind, and how each website collection page moves.
  • Site files: the files left behind.
  • Forms: who each form's workflow email goes to, the forms that add no CRM contacts, the form fixes, and the embedded forms rebuilt as Insites forms.
  • Redirects and form submissions you gave as a file. The tool keeps its own copy for the new migration.
  • What the load carries: whether the code, the files and the passwords are copied, and which constants.
  • To do ticks about the old site, such as the Squarespace gift card list you downloaded.

What is not carried

These belong to the staging instance, not to the site, so the production move starts without them. The plan lists each one under Not carried from the first move.

  • The staging instance's key, its sender address, its domains, its DNS jobs and its cutover steps.
  • Its watch and its nightly sync, its GitHub branch, and the test accounts for the signed-in checks. Add the test accounts again on the Signed-in checks step.
  • To do ticks about the staging instance, such as setting up its email or its integrations. On production they are still to do.
  • Code files kept at the staging version. Changes made on staging after its load are on staging only, so production gets the old site's version. Copy each change across, or make it on the old site first.
  • People accepted as they are on staging. That said who already had an account there.

When the old site has changed since

The tool reads the old site again, so the production move copies the site as it is now. It never guesses a decision nobody made:

  • New since the first move: needs a decision. A database, code file, form, constant or collection the old site has now and did not have at the staging move is listed with what the plan does with it as it stands, for example copied or not copied. Change it on Transform if that is not right.
  • Decisions that no longer apply. A decision about something the old site no longer has is listed. It stays in the settings and changes nothing. A rule for a single row that is gone is asked about as any plan asks about it.

The two migrations

Each migration links to the other at the top of its page. They are two migrations: each has its own keys, its own copy of the old site and its own report, so closing or deleting one never touches the other. Activity records who moved it again, on both.

The staging instance is not touched. Moving again only reads the old site. To bring staging up to date instead, use the final sync on the staging migration.