Tutorial
Migrate a Webflow site
This walks through a whole migration of a Webflow site to a new Insites v6 instance: its collections and every item in them, every published page with its design, its images and files, its redirects and sitemap, and what people sent through its forms. A site of around 30 pages and 30 collection items takes about half an hour. You can close the page at any point: the migration carries on, and you come back to it from Migrations in the menu on the left.
- A new, empty Insites v6 instance, the Developer role on it, and an access token from its CLI tab in Insites Console. How to create one.
- A Webflow site API token for the site, made by an administrator of the site, with CMS, Pages and Assets set to Read-only, and Sites and Forms too if you can. How to make one.
- Nothing to export. What people sent through the forms is copied with the token, and the tool finds the site's redirects itself.
How the wizard works
A migration has seven stages: Source, Destination, Transform, Plan, Load, Verify and Launch. Each stage is split into a few short steps, listed down the side of the page. The footer at the bottom always holds Back, where you are, and the one thing to do next. When the next thing cannot be done yet, the footer says why. Nothing is written to the new instance until you approve the plan and type its code.
1. Source: connect the Webflow site
- Sign in and click New migration.
- On Where are you coming from?, choose Webflow site. A platform that is not listed? The last tile, Request a platform, tells us which one you use.
- The next screen asks only for The site's address: the address visitors use, for example
https://www.example.com. The tool reads the site's Webflow id from its home page. Press Next. - The key screen shows how to make a Webflow site API token, step by step. Paste the token into Site API token and press Connect and check.
The tool checks each permission the token has and lists them. Can read is what you want. Missing means a required one is not set, so make a new token with it. Not given means a recommended one is not set: the migration still runs, and the list says what it cannot read. A token made for another site is refused before anything is read.
What it holds then groups the site the way Webflow does: CMS collections, Assets, Pages and design, Domains and redirects, Forms and Ecommerce. Each part says whether it is copied. Draft pages and password-protected pages are counted and stay behind, with the reason. Products are not copied in this version.
2. Destination: connect the v6 instance and start a dry run
- Press Log in to Insites Console. Console opens in a new tab. Create a new, empty v6 instance there (how), come back to the tool and press Next.
- In Insites Console, open the new instance and its CLI tab. Press Get my token and copy the token.
- Back in the tool, give the v6 instance URL, paste the token into Console access token, and press Connect and check. The tool checks your role and that the token is for this instance. More on the token.
- What it holds shows what the new instance has already. A new one holds only the platform's own starting content.
- Choose Dry run and press Read the source.
A dry run reads both sides and reports exactly what a migration would do. Nothing is written anywhere, and it can become the real migration later without reading the site again. The tool reads every collection through the token, and every published page from the live site, with the files each page loads. A progress bar shows while it reads.
3. Transform: check where everything goes
The stage opens with Analyze, which reads the whole site, and Next opens once the read is done. Most Webflow migrations need no changes after that. Each step says first whether it needs a decision.
- Databases: each collection becomes a table in the Data module, named after the collection.
- Pages and code: each published page, with the address it keeps, and each collection page as an Insites CMS collection, with its list and details layouts.
- Site files: the site's own files, by folder: the asset library, and the stylesheets, scripts and images the pages load. Every one is copied unless you untick it. An image a collection's text names is not listed: it is copied with its row.
- Redirects: the redirects the tool found on the live site. To be sure of every one, export the list in Webflow from Site settings, Publishing, 301 redirects, paste it in, and press Use this list. A redirect in your list wins over one the tool found for the same address.
- Forms: every Webflow form, recreated in the Insites form builder with the table it saves to. It says Past submissions are copied from Webflow's API with the rest of the site, so there is nothing to add. Type who each form's workflow email goes to: Webflow's API does not say. The autoresponder is made switched off for you to turn on later. A form from another service embedded in a page, such as JotForm or HubSpot, is not rebuilt: it is kept as it is, still sending to that service, and What it holds lists it under Forms from another service. More.
- CRM, Events, Locator and Other: a Webflow site has none, and each step says so.
- Users: the tool does not read the people who sign in to a Webflow site, so none are copied, and the step says so.
- Ecommerce: Coming soon. The tool does not read a Webflow store yet, and the step counts its products.
- Advanced: rules for an unusual migration, to change a name, fix a value, or leave a row out, each with a reason. They start closed, and most migrations need none of them.
On the last step, Advanced, press Continue to the plan. Your choices save by themselves as you make them. Every setting.
4. Plan: read what will run
- Summary and decisions: the numbers, and anything that would stop the load, each with a button to fix it. Each fix asks why, and the reason goes in the report. More on resolving the plan.
- What the load carries: the pages and the files.
- Fixes: anything the tool can fix for you, shown line by line, or a note that there is nothing to do.
- Changes and what is not copied: what changes on the way, and what is not copied. Look for two Webflow things here. A collection page the tool could not rebuild from the item's fields is named, for you to rebuild. A collection list the tool could not work out keeps showing what it showed when it was read, and only that list: the other lists on the page still read their tables. To rebuild such lists once a later version can, run a final sync while the migration is open, or start a new migration to the same new instance once it is closed. Each form on a copied page is listed as recreated in the Insites form builder, and one whose workflow email goes to nobody yet is named.
When the plan reads right, press Run it for real on its last page. It uses this exact plan.
5. Load: confirm with the plan code
Confirm the load shows the plan's code. Type it into Plan code and press Load. The tool loads the collections, the files and the pages. You can close the page: we email you when the load finishes, and again when the checks finish. If the load stops, the page says why in plain words, and it can carry on from where it stopped.
6. Verify: see what was checked
The checks start by themselves when the load finishes, and usually take a few minutes. These matter most for a Webflow site:
- Records, read again from the source: the tool reads Webflow again, and every row matches the site as it is at that moment.
- Links between records: every reference field points at a row that is there.
- Pages say the same: every page, every collection item page included, says the same words on both sites.
- What pages load: no page or stylesheet still loads a file from Webflow.
- Redirects: every redirect, found or given, sends visitors to its page.
Verify is five steps. Result opens with two figures: the records copied, out of the records on the old site, and the items checked that passed, out of every item checked. Then the table of what was checked. Send to GitHub sends the new site's code to your repository, where GitHub is connected. Things that need you takes you through what failed, one thing at a time, each with one thing to do about all of it. Worth a look has the page photographs and the errors the new site logged, which do not decide the verdict. The Verification log holds every verification in full. Anything you must do yourself is on the To do list too. After you fix something, press Check again. The checks.
7. Launch: the launch, in time order
Launch opens with a timeline of the launch and marks where you are. Each job only a person can do, written for this site, sits in the step it is done in. Tick each one off as you go. When the load finished, Load asked whether to sync every night until cutover; the choice is under Before cutover too.
- Before cutover: let the site's Adobe Fonts kit serve the new domain, only if the check found that the kit refuses it; and check each form recreated in the form builder, then read its autoresponder and switch it on.
- Cutover: going live, in order. Stop editing in Webflow, run the final sync so the new site has the last changes, move the domain, and check the site on its domain. Its jobs add the site's domain to the new instance in Insites Console, point its DNS there, and point the site's other domains there too. Copy first, then cut over.
- After cutover: show the site's editors where each collection is now, in CMS > Collections in the instance's admin and in Data, and that to take an item off the site they empty its Published address (Draft and Archived are kept for reference and hide nothing); tell search engines about the new site; and keep the Webflow site for two weeks before ending its hosting plan.
- Watch: for 14 days after cutover, every page and the log, every 6 hours, with a summary email a day.
- Report: two PDFs, each kept in the tool as well as downloaded. Summary for your client is one or two pages for the site owner, with the Insites logo and no check codes: the old address and the new, what was copied, the result in one line, what was not copied and why, and what is left to do. Send it as it is. The Technical report is the whole migration: every check and what it was first tried on, what was left behind and why, and every decision with who made it and when. The reports.
- Close: when the new site has run cleanly, press Close the migration, type the old site's address, or its Insites name, which the dialog shows, and press Close the migration. The migration becomes a record, and the tool removes its copies of both keys. Until then, a load can be rolled back.
Last, revoke the token in Webflow, in the site's Site settings, Apps & integrations, API access.