Skip to main content
Theme

Updates

Changelog

Versions before 0.1.0 were numbered afterwards, in the order they shipped.

November 19, 2026: version 0.8.92

  • You stay signed in through a long load. Signing in with Insites Console now lasts 12 hours without a visit, and an open page keeps you signed in, even in a background tab. If you are signed out, the page says your migration keeps running, lets you sign in again in a new tab, and carries on by itself with nothing lost.

November 18, 2026: version 0.8.91

  • Behind-the-scenes upkeep. The tool now keeps its own sign-in to Console fresh by itself. Nothing changes in how you use it.

November 18, 2026: version 0.8.90

  • The watch now says which pages it opened when the new site logs an error with no file. On one move the new instance logged "Could not find Table with name: modules/logs/form_debug_log" a few seconds after each look, and the watch said only "The new instance logged a GraphQLMutationError", so the team could not tell where to look. Such an error now names the pages the watch opened at that time, says it names no file of the site's own code and may come from an installed module, and, when it asks for a missing table, says whether an installed module has that folder. It is still counted and filed as a Teamwork task, because any visitor opening the page would cause it too.

November 18, 2026: version 0.8.89

  • The plan no longer asks you to rewrite code the move wrote. The not-found page's redirect line and the form builder's workflow and autoresponder emails use parts of the v6 CRM and Forms modules, which the new site has. The plan named them as parts the new site lacks and asked for them to be rewritten before cutover. It now names only parts that are really missing.

November 18, 2026: version 0.8.88

  • Page numbers below a collection list page answer 404, as on WordPress. A moved page that sits at the address a custom post type's items sit under, such as /education above /education/<item>, or a post type archive, is now treated as a list, so an invented page number below it, such as /education/page/2/, answers 404 rather than redirecting to the page. The Page numbers on lists check also counts the old site showing the same page at a page number with no canonical link (as a page set to noindex does) as a match for a redirect to that page.

November 18, 2026: version 0.8.87

  • Every moved WordPress page answers page numbers as WordPress does. A page number below a static page, a post, a child page or a collection item page, such as /privacy-policy/page/2/ or /hello-world/page/2/, now redirects with a 301 to the page itself, where WordPress redirects or shows the same page. Below the blog page and a category, tag or author list, a page number the old site does not have still answers 404. The Page numbers on lists check now compares where a redirect leads, not only its status, and counts the old site showing the same page as a match for a redirect to it.

November 17, 2026: version 0.8.86

  • A moved WordPress page no longer answers page numbers the old site does not have. An address below a moved page, such as /author/<name>/page/9/ for an author with one page of posts, now answers 404, as it did on WordPress, instead of showing the first page. Every page of a category or tag list now moves, not only the first. A new advisory check, Page numbers on lists, asks each page for the page number past its last on both sites and reports any difference.

November 17, 2026: version 0.8.85

  • A final sync is refused up front when every earlier copy of the old site has expired. Before, it started, failed as it began reading, and the Cutover page could still show the final sync as done. Now it says why and suggests a full run of the same site onto the same instance instead.

November 17, 2026: version 0.8.84

  • WordPress author pages now move, and a link to a page you chose to leave behind no longer fails. Every author with published posts keeps their author page at /author/<name>/, every page of it, copied as the category pages are. An author with no posts gets a redirect from their old author page to the blog page, or the home page when the site has none. The Links on every page check now says a link to a page you left behind is left behind by your choice, rather than failing it.

November 17, 2026: version 0.8.83

  • Elementor Pro submissions of old forms no page shows now move. Each old form's submissions go to a table of their own, named after the form, with no form rebuilt and no email, and the plan says they are kept as records. Source records accounted for now counts every submission Elementor Pro keeps.
  • A sync no longer copies scripts, stylesheets, SVGs and fonts again when nothing changed, and a file the old site does not serve no longer fails the checks. A source that sends those files compressed gave no size for them, which was read as 0 bytes, so every sync sent each one again. Rows the source gives no dates, such as WordPress categories and menu items, are no longer brought up to date on every load. ASSETS, INVENTORY and ADDRESSES now class a file the old site answers 404 for as broken on the source, as PAGELINKS does a link that fails on the old site too, instead of failing on it.

November 17, 2026: version 0.8.82

  • Elementor Pro forms on a WordPress site are rebuilt in the form builder. Each one keeps its look and its field names, saves what people send to its own table with a workflow email, and its past submissions come from Elementor Pro or its CSV export.
  • WordPress files with a no-break space in their name, or named inside a page's script data, now move. A file such as a Mac screenshot ("8.32.27 PM", where the space before PM is a narrow no-break space) was cut at that space, so it was not copied and the page address was broken. A file a theme or plugin names inside inline JSON with escaped slashes (for example a loading.svg) was pointed at the new site but never copied, so the address check failed on nearly every page. Both are now copied and pointed at their copy.
  • A final sync of a site that has not changed writes and copies nothing. The redirects the move made keep their ids instead of being written again, a stylesheet is sent again only when its text changed, a file the old site no longer serves is not read again on every sync, and a WordPress row that links a file from the site's root no longer fails the source check on every run.

November 16, 2026: version 0.8.81

  • Columns that hold another row's id now follow the row to its new id. When a copied row takes a new id on the new site, any column that points at it, such as a data source picker holding one id or a list, is rewritten to the new id, in the load and in every final or nightly sync. An id that names no copied row is kept and listed in the load log. The References check now also confirms, on an Insites source, that each of these ids names a row that is there.
  • Columns that hold another row's id now follow it on an Insites v4 source too. A column whose table was renamed on the move (for example modules/ins_database/ to modules/ins_databases/) is found through the same rename, in the load and in the References check. A picker named by its v4 type is recognized, and a picker that stores another field's value instead of the row's id is left as it was.

November 16, 2026: version 0.8.80

  • The checks no longer open a page that may change data. A test page on an old site created a record with dummy data every time it was opened, and the page and screenshot checks opened it on both sites. A page is now skipped, on both sites and in every check, when its name looks like a test (test, controller, debug, sandbox, seed, demo-data) or its code writes data when it opens (a graphql mutation, or a call to a create, update or delete function). The plan lists each one with its reason, and one To do job, Pages not opened because they may change data, names them so you can delete or keep each. They count as not checked, never as failed.
  • The code copy now says when the source was read, and checks it against your repository. Where a GitHub repository is linked, Pages and code and the GitHub step show when the source code was read and the repository's latest commit then, and warn "Re-read the source before copying" when the repository has newer commits. One To do job, "Files on the old site that are not in your repository: drop or keep", lists the files only the old site has, grouped by folder, and a button leaves them behind. Nothing is left out unless you choose it. With no repository linked, the page says the comparison was not possible.
  • The config.yml comparison now flags only settings that make a difference. Blank, false, "default" and not set count as the same, and a setting for a feature the site's code does not use is left out. The advice now says to set the value on the instance, and warns that deploying config.yml replaces the whole file.
  • The To do job that updates Insites modules now names each module. It lists every module that is behind, with its installed version, its latest version and where to update it (the Modules tab in Insites Console).
  • Files in the tables of an Insites module are copied the same way as files in your own tables, and Verify names any file link that does not open. A product image in the Ecommerce module could be left on the old site, so the image answered 404 on the new site while the check stayed quiet. The copy now reads a module table's file columns in every shape the old site stored them. The Files check opens the link of every one of them on the new site and fails with the table, the column and how many files did not open.

November 15, 2026: version 0.8.79

  • A file you accepted as missing stays accepted on the next nightly sync and the final sync. Until now the same accepted file was flagged again every night. An acceptance now holds until the old site names a different file on that row.
  • The plan now stops on two pages that answer at the same address. It used to compare your pages only with the pages already on the new site, so two of your own pages at one address were found only when the load was refused. It now finds them before the load, including addresses that differ only by letter case, a trailing slash, /index, an escaped character (caf%C3%A9) or a dynamic name, and a page that meets a CMS collection item. A GET page and a POST page at one address are still fine.
  • Verify now fails a page that shows a Liquid error from a missing partial, and names the partial. A page that calls a shared part the new site does not have no longer passes because a To do job covers it. The plan also lists every such partial, with the pages that call it, in one To do job: change the code, then check again.
  • The final sync step is ticked only when the sync finishes. It used to show done the moment the sync started, even if it then failed. It now shows in progress while the sync runs, done once it is verified, and not done, with the error, if it fails. A long error from recording a site's migrations is also kept in full (up to 4,000 characters) instead of being cut at 240; the To do job shortens it with an ellipsis.
  • A file the new site already holds is copied again when its size is not the old site's. Before, the load left such a file alone unless it was served as the wrong type, so a file replaced on the old site, or cut short by an earlier copy, stayed as it was. It now compares sizes and copies the file again when they differ. Files of the same size are left alone, and a file whose size cannot be read on either side is not copied again.

November 15, 2026: version 0.8.78

  • A nightly sync no longer stops over files of an Insites v4 module that v6 replaced. Files in modules such as insites_permission_manager, insites_core, insites_site_manager and insites_event_stream are left to the platform, so they no longer collide with the v6 pages in the plan. Files you wrote yourself are still copied.

November 14, 2026: version 0.8.77

  • Webflow shops can move. Where Insites switches it on, a Webflow Ecommerce site's products, SKUs, stock, categories, orders, payments and customers move into the Insites Ecommerce module and the CRM, with a cart and a Stripe checkout on the new site. Discount codes, shipping and tax settings and the payment connection are named on the plan with what to do, because Webflow's API does not give them. Until it is switched on, a Webflow shop is counted and left for you to set up, as before.
  • The Git repository job now matches Insites CRM 6.1.7. On a new instance with CRM 6.1.7 or later, the To do list says to link the repository in Insites Console and check the Git Repository page's Status and Last commit, instead of the SSH form that page no longer has. An old instance on CRM 6.1.7 or later keeps its link in Insites Console, which the migration cannot read, so the job asks you to check its Git Repository page rather than taking it as not linked.
  • Connect GitHub, in place of Send to GitHub. Where Insites switches it on, the Verify step after Result is Connect GitHub. It explains that the code lives on the new instance and links to Insites Console, where the instance is linked to one GitHub repository both ways: CMS saves are committed, and pushes are deployed. The Report step has the same card, the To do list has a job for it after cutover, and the tool no longer sends code to GitHub itself.

November 14, 2026: version 0.8.76

  • Copy all again no longer stops with a timeout when the old site is slow. The tool now answers at once that it is still copying, and carries on in the background while the page keeps showing progress.
  • When the AI account cannot be used, the page review says so once. If the AI account has no credit left, rejects its key or reaches its limit, the migration no longer shows a failure for every page. The AI page review is marked not available, one To do job lists the pages to check yourself, and pressing Check again later runs the review once the account works again. Insites is alerted once an hour.

November 14, 2026: version 0.8.75

  • Insites v4 forms now reach the thank-you page and keep their emails, and a reCAPTCHA setting with no options stays on. A form that added a CRM contact when sent used to show an error page after the submission saved, because the move pointed it at a file the v6 CRM does not have. It now calls the v6 CRM's own contact step (CRM 6.1.6 or later), and its two CRM emails stay on the form. A form notification with no v6 copy is now a job on the To do list that names the form. A form file that names reCAPTCHA v2 with no options is now moved with reCAPTCHA on, not off.
  • Old storage addresses written with encoded slashes are now moved and checked. An address such as .../instances%2F431%2F..., which Open Graph image tags often hold, is now pointed at the copy on the new site like the plain form, and the Links check lists any that remain. Before this, they were missed and would have broken when the old instance shut down.
  • The advice for private Webflow form files now points to the right setting. Webflow moved Restrict uploaded file access to Site settings, under Apps & Integrations, so the To do job, the file reasons and the Webflow docs now say so. They also say that only turning the setting off needs the client's OK: downloading the files yourself and uploading them exposes nothing.
  • The "Update the Insites modules" job ticks itself once the modules are current. The job now lists each module with the version installed and the version needed, for example "CRM: installed v6.1.5, needed v6.1.6". When you press Check again on Verify or Launch, or the daily watch looks, the tool reads the new instance's installed module versions. When every module the job names is at or above the needed version, it marks the job done by the migration tool. A job you ticked yourself is never changed, and a read that fails settles nothing.

November 13, 2026: version 0.8.74

  • The emails and connections check no longer reads as failed while they are held. Holding them until cutover is the plan, so while they are held the check now passes as a note that says how many are held. It still fails if an email or connection sends when it should be held, or cannot be found on the new site.

November 13, 2026: version 0.8.73

  • The screenshot check now reads every page it meant to read with AI. A page the AI had no time to read in one step is photographed again and read in the next step, instead of keeping its pixel result as the answer.

November 13, 2026: version 0.8.72

  • The bound-fields check no longer calls a page a copied list because it shows the company's name. A value that every item of a collection shares, such as an author field that holds the company's name on every news item, names no item, so a page that shows those words in its header or footer is no longer flagged as a fixed copy of that collection. A list copied as text is still flagged by the fields that differ from item to item.

November 12, 2026: version 0.8.71

  • The files check now counts every form file the move copies. On a Webflow site with over a thousand form files, the check missed 31 of them because of their file names or types, so those files were never checked. It now checks every file the move counts.

November 12, 2026: version 0.8.70

  • The advice for private Webflow form files now warns about privacy. While Webflow's Restrict uploaded file access setting is off, anyone with a file's link can open it, so the To do job and the docs say to get the client's OK first and keep the time short. They also offer the safer way: download the files from Webflow while signed in and upload them to their records yourself, and note that Webflow may keep older files private whatever the setting says.

November 12, 2026: version 0.8.69

  • Files sent through a Webflow form that Webflow keeps private are explained, listed and can be copied again. When the old Webflow site keeps form files behind a Webflow sign-in (its Restrict uploaded file access setting), the site's API token cannot open them, and the files were left behind with only a number. Now the To do job says why and what to do: turn that setting off in Webflow, press Copy again on the files card, then turn it back on. The files card on the Verify step also lists every file that has no upload on the new site, with its Copy again button, where before it said "The check listed 0 of" the total. Copy all again stops each step in time, so the page no longer waits past 60 seconds for a slow record. COVERAGE no longer counts the redirects the move makes as source records loaded, so its loaded number matches the rows on the new site.

November 12, 2026: version 0.8.68

  • Files you added inside an Insites module folder are now copied, not dropped. A page or other file someone put in a folder such as modules/insites_api/ (for example a webhook page) was left behind with the module's own files, with no word. The plan now names each one as a custom file inside an Insites module folder, copies it to the same path, and counts it as yours on INVENTORY. You can still leave one behind under Code files left behind. If such a file holds a secret written into a public page, the plan says so without showing the value.
  • Image versions now work after a move, and Insites v4 addresses arrive in Location 1. An uploaded image with versions (Mobile, Desktop, List-View, OG and so on) is now fetched by the new site as an image, so the new site builds every version, and the old site's version addresses are no longer kept. The FILES check now opens each image version and fails, by name, on one that does not open. On an Insites v4 move, an address held in Global Content as single fields (Address Line 1, Address Line 2, City, State, Post Code, Country) now fills Globals > Locations > Location 1, any field without a clear match is named on the plan, and COVERAGE fails on a Global Content value that has no field on the new site.

November 12, 2026: version 0.8.67

  • Insites v4 moves now copy every Global Content image. A Company Logo or Company Icon that a v4 site kept as an image address, rather than as an uploaded file, now arrives on v6 as a file, and the field points at the new copy. The verify step's COVERAGE check now fails, naming the field, when a file field the old site had set holds no file on the new site.

November 12, 2026: version 0.8.66

  • A final sync more than a week after the copy now runs. When the copy of the old site the tool kept from the earlier run has expired, the final sync reads the whole old site again instead of stopping. It takes longer and still loads only what is new or changed. A final sync that stopped this way wrote nothing, and its page now says to press Carry on, not to plan a new migration.

November 12, 2026: version 0.8.65

  • A page the browser could not photograph is tried again, and its job ticks itself once it can. When a photograph fails because the browser closed, was busy or lost its session, Verify now tries again, up to two more times, before it adds a job to look at the page by eye. A page that answers with an error of its own, such as 404, still gets the job at once. If a later Check again photographs the page, the job is marked done by the migration tool. A job you ticked yourself is never changed.
  • Log tables are no longer compared row by row. The Rows check and the Links check skip the site's own job run and system log tables, because the site keeps writing to them and their text is history, such as a log line naming a deleted file. Each check says how many rows it left out, and the Inventory and Coverage counts still include them.

November 12, 2026: version 0.8.64

  • The screenshot check stops asking the AI once the AI service turns the account away. When the AI account had no credit left, every page was still sent and refused one at a time. Now the first refusal is enough: the rest of the pages keep their pixel result and say why the AI did not read them.
  • The Crawlable check no longer fails a sitemap on a move from Insites v4 for listing more pages than expected. Insites v4 pages do not say which belong in the sitemap, so the migration expected none, and the watch emailed a failure for a sitemap that was fine. When no pages were recorded, the count is now skipped and the check adds a note instead.

November 12, 2026: version 0.8.63

  • The reCAPTCHA job ticks itself once the keys work. Each time you press Check again on Verify, the tool opens every page the job names on the new instance. When none shows "can't find configuration for CAPTCHA" and the new site's log has no such error, the job is marked done by the migration tool, so you no longer have to come back and tick it.
  • Domain and DNS jobs tick themselves once the domain has moved. When you press Check again under Checks on the new site in Launch, and once a day while the tool watches the new site, it opens each domain an open domain or DNS job names. When the domain answers from the new instance, the job is marked done by the migration tool, so you no longer have to come back and tick it.

November 11, 2026: version 0.8.62

  • More of the old site's reads wait out a short network outage. The sitemap, robots.txt, stylesheet, file and redirect checks of the old site, and the reads of a GitHub repository, now ask again for up to about a minute when the network drops, as page reads already did. Before, one dropped connection in a sitemap or robots.txt read was taken to mean the site had none. If the network stays down, the migration stops with "A network outage stopped the tool reaching the old site": press Carry on or Run again.

November 11, 2026: version 0.8.61

  • Reading the old site waits out a short network outage. When the network drops for a moment while the tool reads the old site's pages and files, it now asks again for up to about a minute before giving up, so one brief outage no longer fails the whole migration. If the network stays down, the migration stops with "A network outage stopped the tool reaching the old site": press Carry on or Run again. An answer from the site (404, 401) is reported at once, as before.

November 11, 2026: version 0.8.60

  • The FILES check waits out a short network outage. When the network drops for a moment, the check now asks for each uploaded file again for up to about a minute before giving up, so one brief outage no longer fails the check. A file that still cannot be reached is reported as "could not be reached (network), the file was not proved missing". That is not a missing file: press Check again. A file the storage answers for (404, 403) is reported at once, as before.

November 11, 2026: version 0.8.59

  • Going ahead with a failing check now settles it on Result. After you press Go ahead with this check failing (or give a reason under Go ahead anyway), the failure leaves Not confirmed and Things that need you, Needs you drops, and the migration reads as Verified with your reason kept on the check. It stays that way after Check everything again. A check that later fails for something new asks again. A migration where you already went ahead clears the next time you press Check everything again.
  • Verify links a page's problems that share one cause, and Launch warns when the old site hides itself from search engines. When a page prints an error and also runs off the side on a phone, reads differently or looks different in the photographs, each of those items now says it is likely caused by the error and links to it, so you know one fix may clear both. Nothing is hidden and the counts do not change. If the old site tells every search engine to stay away (its robots.txt says Disallow: / for everyone, or every page carries a noindex tag), the To do list now has a job before cutover to ask the client whether the site should stay hidden, and the Search engines can find it check says this is how the old site is set, not something the move caused.
  • A form you leave behind is no longer drawn by pages that stay, and the plan offers to drop Webflow's sample /style-guide page. Before, a page that still drew a form you left behind showed "Could not find Form with name" on the new site, and Verify reported a Liquid error. Now the plan takes the form out of those pages and lists each one. When nothing links to the sample page /style-guide, the plan says so and points to Transform, Pages and code, where you can leave it behind. It is still copied unless you choose otherwise.
  • The SEO check no longer reports an image tag as changed when only its address moved. When og:image, twitter:image and similar tags now point at the copy of the file on your new site, the check reads both files and passes the tag if they are the same. The check line says how many were compared by file. If the old file cannot be read, the addresses are compared instead and the line says why.

November 10, 2026: version 0.8.58

  • The "This site has no redirects" checkbox is a normal size again. On the Redirects step it had grown to a large blue box on its own line, away from its label. It now sits beside its label like every other checkbox, and every checkbox and radio in the tool now has the same size.
  • The "Pages say the same" check no longer fails on a site search results page. The results on a search page come from the old site's search index and change between two reads, so a verification could fail on /search when the migration had copied it correctly. The page's heading, labels and form are still compared word for word, and its result list is compared by structure. The check line says how many pages were compared that way, and the page stays in the total.

November 10, 2026: version 0.8.57

  • Run again now says when the new site is live, or the old site is gone. Once the new site is live, Run again moves behind a confirm and warns that it would plan over changes made since the load. When the old site cannot be found or read, Run again is not offered, so no plan starts that would fail.

November 10, 2026: version 0.8.56

  • Pages moved from Insites v4 are listed in the new sitemap again. A v4 site's pages were left out of the v6 sitemap, so search engines found none of them after the move.

November 10, 2026: version 0.8.55

  • Releases are tested more reliably. The sign-in used for testing is now checked every 4 hours, and the final checks before a release run faster. No screen or step changes for you.

November 9, 2026: version 0.8.54

  • The watch says when a page no longer asks visitors to sign in. A page that sent visitors to sign in, or turned them away, when the migration was verified, and now opens for anyone, is flagged as high priority. The watch says so plainly, instead of only "now answers 200", and tells you to check the page's authorization policy.

November 9, 2026: version 0.8.53

  • The activity log now says why Crawlable failed. A failed Crawlable check in the launch steps or the watch now names the first problem it found (for example, the address that did not answer) in the run's activity log, so a check that keeps failing can be understood without opening each run.

November 9, 2026: version 0.8.52

  • Webflow product pages are rebuilt from the database. Each product page now reads its product and its default SKU from their rows: the price, the gallery of the SKU's images, the compare-at price, and tags such as "New" or a discount, shown by the field that shows them on Webflow. A product card's background picture is read the same way, including files with brackets in their names. Before, these pages and the product list beside them stayed fixed copies of the old site, so changes made in the admin did not show.

November 9, 2026: version 0.8.51

  • Webflow lists sorted by a reference, then by date, now read the database. A list sorted by Category and then newest first, such as a blog page or the "more posts" list on each post, used to stay as it was on the day it was read. It now reads its items, sorts them by the category's name and then by date, and leaves out the current post and applies the limit after sorting, so posts an editor adds show up in the right place.
  • Webflow item pages print a field every item shares from that field. When every item in a collection holds the same value, such as a Type of "Family House" on every project, each item page now reads it from the item, so changing it in the admin changes the page instead of leaving the old text in place.

November 8, 2026: version 0.8.50

  • Product lists and lists filtered to one category now read from the database. A Webflow list of products prints each product's price from its row, kept as the text the site prints (for example "$ 550.00 USD"), and a list filtered to one fixed item, such as "Category contains Rent", keeps that filter. Before, both stayed fixed copies of the old page, so items added or changed in the admin did not show.

November 6, 2026: version 0.8.49

  • Settings you saved earlier now get the short-name fix. A move whose settings were saved before October 23 kept calling forms such as recover_password by their short name, so the new site showed "Could not find Form". Every run, including the nightly sync and Run again, now writes the full name, such as modules/website/recover_password. Nothing you chose is changed.
  • Copy this one again puts the hold back on a held email. A form email held until cutover that was switched on again on the new site stayed on after Copy this one again, with only "2 fields still differ" to show for it. Copy again now writes the hold on its own, leaving the sender and layout as the new site has them, reads it back, and says plainly when the email still sends.
  • Ask about this migration now says where to move a run to another instance. Asked how to move the same run into another instance, it answered that it could not name a button. It now knows that Move again to another instance is on Launch, Close, and on the Where to go from here card of a load that was rolled back, and that Run again with the latest fixes is on Verify, Result.
  • A page the new site was too busy to save is tried again. When the new instance's database timed out while saving a page or other code file, the move listed the file as refused and asked you to fix code that had nothing wrong with it. The tool now waits and tries again, checks first that the earlier try did not land, and if the database is still too busy says so plainly and tells you a final sync copies it.
  • A copied Webflow page answers only at its own address. An address below it, such as /modules/old-name under /modules, now answers 404 as on Webflow, so the redirects set for those addresses work. A paginated collection list that starts after its first items shows as many items a page as on Webflow, a frozen collection's own address answers 404 and replaces a collection page an earlier move left there, which listed its items a second time in /sitemap.xml, and Verify's suggestion for a redirect that loads a page says when a final sync helps and when it does not.
  • An image file name is no longer replaced with a field. When a collection item's slug was the same word as an image's file name (zapier.svg for the item "zapier"), the moved page printed the slug in its place, so the image address broke. A file name now stays as it was written. A text that is really a field still prints from it.
  • Verify now compares SEO tags on a move from a website, such as Webflow. Until now only Insites moves were checked, so a canonical link that changed from a full address (https://www.example.com/pricing) to a short path (/pricing) went unnoticed. SEO now lists it, with the old and the new value.
  • Run again now clears old text left in a file column by an earlier load that stopped. The files are copied into those rows and the final check can read them, instead of every file in the column failing to copy.
  • A Webflow image with brackets in its name now copies with its extension. A shop product image named like "photo (1).jpg", used as a page background, was read as "photo (1" and copied without ".jpg", from an address Webflow refused, so the asset checks came up two short. The tool now reads the whole address, and asks again with the single-encoded address when Webflow refuses one that was encoded twice.
  • The Crawlable launch check follows a robots.txt redirect to the same site's other host. When www redirects robots.txt to the bare domain, or the other way round, the check now tests the host it leads to, once, and adds a note saying so. It no longer fails with a false alarm and no longer sends a repeat email. Any other redirect still fails.
  • Files sent through forms are now checked where the move copied them. A resume or other file people sent through a Webflow form is looked up in its row on the new site, so files that were copied no longer read as still on the old site. A file not copied yet says Run again copies it, and a file the old site would not give is listed on the To do.
  • The plan now tells you when a file column still holds text from an earlier load that stopped. Under Worth knowing it names the column and how many rows, and says the load clears that text (saved first, so Roll back restores it) and copies each file from the old site.
  • The Addresses check no longer fails a page made to answer "not found". When a collection has no page of its own at its address on the old site, the move writes one there that answers "not found", as the old site does. Verify called that a failure. It now checks that page the way it checks the site's not-found page: what it loads, not whether it answers.
  • A file whose name holds a percent sign now opens on the new site. The new instance does not encode "%" in a file's address, so a file named like "Report%20Q3.pdf" answered "not found" and its row showed as different. The tool now stores such a file under its decoded name ("Report Q3.pdf"), and checks it under that name.
  • Pages from a Webflow Ecommerce site are copied again. Webflow prints a currency template in every page head that only looks like Liquid. The tool keeps it as plain text, but the code check still read it as Liquid and held back almost every page and partial as code the new instance would refuse. The check now skips text kept as plain text, so these pages, their collection templates and the 404 page are copied.
  • Forms that share a name, or appear twice on one page, keep their own fields and style, and images whose names hold an encoded percent sign open on the new site. Two different Webflow forms with the same name, such as the default "Email Form", are each placed where they were, including on a collection's item pages, so no form loses a field. A page that shows one form twice in two styles keeps both styles. A collection image whose Webflow address holds "%2520" (a name Webflow itself saved with "%20") is copied under its readable name, so it opens instead of answering 404.

November 6, 2026: version 0.8.48

  • An error the old site logs too is now recognized when the platform suggests different names on each site. A missing form or query whose error ends "Did you mean one of" was listed as yours to fix, because each site suggests the names it has. It is now listed as the old site's, so it no longer asks you to fix something the migration did not cause.
  • The bound-fields check no longer calls a form's submissions a fixed copy of a list. A table that holds what visitors sent through a form that was not rebuilt in the form builder is no longer treated as a list a page shows, so a careers page that shows a submitted answer is not flagged.
  • A redirect under a copied page's address now works when redirects are kept in Settings. A page already answered at the longer address, so the new site showed that page and never reached the redirect. Such a redirect is now also written as a page that redirects, and it still appears in Settings > Redirects. The plan says how many were also written as pages.
  • A check step that is cut off and resumed no longer counts a check twice. The saved draft of the checks now holds its own copy, so resuming a step that stopped part way through a unit does not add that unit's checks a second time. The confidence count no longer counts the same pages twice.

November 5, 2026: version 0.8.47

  • The source check no longer fails on a row added during a run. A form submission or other row created on your old site after the capture is now counted as added after capture, and the final sync carries it. A row that existed at capture and is missing still fails.
  • Insites v5 moves keep sitemap settings, forms, migrations and trigger conditions as they were. A CMS database layout's is_sitemap_enabled: 'true' is stored as a real true, so its list stays in the v6 sitemap. A page that had no sitemap setting gains none. A form that saves to modules/insites_core/crm_company moves to the v6 CRM's table instead of stopping the plan. A migration whose body the new instance refuses stays recorded as run, and its file says plainly that the body was skipped. A trigger condition of t or f is written as true or false, and the code check reads it as matching.
  • A Run again plan no longer shows two notes that contradict each other. When a row was changed on the new site after the old site's copy, the plan said both that loading would write the old values over it and that it would be kept. A Run again keeps such rows as the new site has them, so the plan now says only that.
  • A text column that becomes a file column no longer stops the load when its rows hold a Webflow form file's details. The old text is cleared before the column changes, and a load that already stopped there clears it when you carry on or run again, so each row gets its file. A file that cannot be copied is named after the load instead of stopping it.

November 5, 2026: version 0.8.46

  • Older form submissions from a Webflow export now match the API's copies when the export wraps values in quote marks. Some exports keep quote marks around a value, single or doubled, straight or curly. These no longer make a submission look new, so it is not added a second time. The saved value keeps its quote marks. Two different submissions still stay two.
  • A form's file field kept as text by an earlier run now becomes a file field. When an earlier move kept each file sent with a Webflow form as text on the new site, such as the resumes on a Careers form, a Run again stopped with only Leave the field out, because the text was Webflow's record of the file and not its address. The plan now recognizes that text as the same file the migration copies and makes the field a file field, with each file copied into its row. When some text is the address of a file the migration does not otherwise copy, the plan offers Make it a file column, which copies each of those files from its address. The old text is kept in the migration's undo record, so Roll back puts it back.

November 4, 2026: version 0.8.45

  • A row a rule once left out no longer reads as different after the rule is lifted. When a run again left a row out with a Transform rule, a later sync could report that row's file as differing on the new site, so the sync ended verified with problems. The file the first migration copied is now remembered through the run that left the row out, so the sync finds the row matches. A file that really differs on the new site is still reported.
  • Canonical links keep the site's full address. A moved page's canonical link and its hreflang alternate links now name the site's real domain, as the old site did, instead of a short path such as /services. Ordinary links to the site's own pages are still made relative.
  • A final sync names what it counts. A sync's summary said, for example, "10 deleted on the old site" and "13 of 14 checks passed", with no way to see which records or which check. Now each count opens to its records, by database and old-site id, with a note that a record deleted on the old site is left on the new site, and the checks line names each check that did not pass, with a link to it. A code file the sync kept as the new site has it says so in the Code check, so you know the difference is expected and can keep the new site's version. A sync after a run again no longer counts records as deleted on the old site because an earlier release recorded them under another id: a run again now records every table it copies afresh.

November 4, 2026: version 0.8.44

  • Fixed: Start the final sync and Run again answer much sooner. They no longer look through every migration in the tool to check whether a sync of yours is already running, so the page no longer shows a timeout message for a sync that was in fact started. Background checks that keep your migration's keys also do less work each cycle.
  • The home page has a new look. It opens on the same dark stage as the Insites docs site, with the proof of a real migration counted up in front of you, lists every source as a tile with a Request a platform tile at the end for a site that is somewhere else, sets out why to move to Insites in the docs site's menu style, and shows Insites AI at work on a migrated site. (TW#26980136)
  • A sync never writes over a stylesheet changed on the new site. A website's stylesheet the tool rewrote, such as a Webflow site's shared stylesheet, used to be copied again by every sync, so a CSS fix made on the new site before cutover was removed by the final sync. Now the nightly sync and the final sync leave it as the new site has it when someone changed it there after the migration last copied it, keep every page's link to it working, log it, and add it to the To do for files kept as the new site has them.
  • Fixed: a moved website's stylesheet loads again when the move gives its folders neutral names. The stylesheet's recorded size and the integrity hash each page links it with now follow its new text, so browsers no longer refuse it and leave pages unstyled.
  • The home page now lists Insites v5, Insites v4 and Siteglide among the sources, and says more about what a site gains on Insites and what Insites AI does once the site is there: questions answered from your data, pages and forms built from a description, automations, reports, Slack and Teams, with every change previewed and confirmed first. A section for Insites v4 and v5 customers says what v6 gives them. (TW#26980136)
  • Fixed: a form on a collection's item pages now records the item page's own address in Sent from, such as /portfolio/st-kilda-fc, instead of the collection's address. Ordinary pages record their address as before. The plan also no longer says a form was "not found" on a page whose collection layouts carry it; a page that really lacks the form is still named. (TW#26957003)
  • Older form submissions from a Webflow export no longer duplicate the ones the API already copied. A submission's copy in the export now matches its copy from the API even when line breaks, spacing, email case or phone punctuation are written differently, or the time is a minute off. Two real submissions that say the same thing stay two. When a line is added although only one field differs from a submission already there, the plan names the line and the field.

November 4, 2026: version 0.8.43

  • Older form submissions added from a file now show in the counts, and Transform says whether the plan includes the file. Under each file given on Transform, Forms, the tool says how many of its submissions the plan adds and how many were already copied, or that the plan was built before the file and does not include it yet. Confirm the load counts the added submissions too, instead of only the ones the platform's API gave.
  • A plan built before a release now says so. When a plan waits for its code while a newer version ships, Confirm the load names the version that built it and the version running now, and shows how to get the newer fixes: Run again on the migration it came from, build the plan again from the copy already read, or plan it again from the same source to read the old site again. You can still confirm the plan as it is.
  • A nightly or final sync now fails rows whose dates did not hold in the migration's load. A sync carries the migration's list of rows whose created or updated date the new site did not keep. Before, a row the old site had not changed since was not loaded again by the sync, and the sync's check passed it as saved again on the new site. A sync that brings such a row up to date with dates that hold takes it off the list.
  • Check again now fails rows whose dates did not hold in an earlier load. The migration keeps the list of rows whose created or updated date the new site did not keep, across every load of the run, so Check again and Check everything again fail them as the check after the load does. A later load that brings a row up to date with dates that hold takes it off the list.
  • The load now reports rows whose dates did not hold when it brought them up to date. If the new site does not keep a row's created or updated date after every retry, the load warns with the table and row ids, and the Records check fails those rows rather than counting them as saved again on the new site.
  • The Records check no longer fails a row that was only saved again on the new site. The new site sets a row's updated date whenever someone saves it, even with no change. A row whose values and created date match, and whose updated date is later on the new site, now counts as identical and is counted on its own line. A change to any value, to the created date, or an earlier updated date still fails.
  • The Records check passes a redirect to your own domain that the new site holds as the same page. When an old redirect named your site's full address, such as https://www.example.com/, and Settings > Redirects on the new site holds the same page as a path or on the new site's own address, the check now counts the row as identical instead of reporting it as different. A redirect to another page or another site is still reported.
  • The Redirects check passes a redirect to your own domain that the new site sends to the same page. When an old redirect named your site's full address, such as https://www.example.com/, and the new site sends it to the same page on its own address, the check now counts it as working instead of failing it.

November 4, 2026: version 0.8.42

  • When the source site sends back fewer rows than it said it has, the tool now checks the total again before stopping. The message names the list that came up short.
  • A form table no longer stops a copy when one of its planned ids has been taken on the new site since the plan was made. The row takes a new id instead.
  • Moves from Webflow now copy files uploaded through forms that sit on a page, such as a resume on a job application form. Before, these files were left empty.

November 3, 2026: version 0.8.41

  • Webflow: the field for a form's older submissions now shows on Transform, Forms. The step said to add the form's export below, but no field appeared, because Webflow names a form's database after the form and the field was looked for only under another naming. The field now shows for every Webflow form that saves to a database, on new runs and on Run again, and the file is read before the dry run. The line about adding an export shows only when the field does.
  • Run again with the latest fixes is no longer hidden by a nightly sync that never loaded. A nightly sync waiting at its plan, or one that stopped or failed before loading, wrote nothing, so the run before it keeps its Run again button. When a later run has loaded, the older run now says so in the button's place and links to the later run.
  • Webflow galleries whose images open in a lightbox now show on item pages. A collection page whose multi-image gallery used Webflow's lightbox was left for you to rebuild, so its gallery came across empty. It is now rebuilt from the item's images, and each image still opens in the lightbox.
  • Links to the old instance's files now point at the copies on the new instance. Addresses on the old instance's own address (such as /assets/ files) and on another instance's old CDN storage are changed to the copy the move made, in code and in records. A file that was not copied keeps its address and is listed under the Links check, and links to other sites are never changed.

November 3, 2026: version 0.8.40

  • Webflow form files sent with no address are copied. A past submission's file that Webflow lists by its name alone, such as a resume on a careers form, is now read from Webflow's own address for it and copied into the form's file column.
  • Nothing on the new site is named after the old platform. A website move now calls its layout site rather than webflow or wordpress, puts its pages at their own addresses rather than in a platform folder, and names its tables, forms, columns, partials, files and labels without the platform's name (source_id rather than webflow_id, "Contact form" rather than "Contact (Webflow form)"). A site an earlier move already loaded keeps the names it has, so a Run again or a sync never leaves a second layout or a second copy of a page.
  • Webflow form files sent as an object are found wherever the address sits. When a past submission's file cannot be copied, the plan says how many rows of the form that is in one line, not one line per row.
  • A 404 page your team changed still answers redirects. A sync that keeps the new site's 404 page adds the redirect line at its top, so redirects on Settings, Redirects answer instead of showing not found.
  • Webflow lists inside other lists now read their tables. A page such as a Media page that lists months, each with the articles its Media List field names, shows an article added in the admin, and a multi-reference field is picked by name in the admin.
  • Multi-line Liquid in a file's front matter now stays a literal block. A callback, request headers or redirect that v5 kept as a |- block is no longer turned into one quoted string with escapes and folded lines. The tool also removes spaces at line ends in these values, which changes nothing the Liquid renders.

November 3, 2026: version 0.8.39

  • Test copies can no longer email a real person. Before a test copy is planned, every email address in the people and data it copies (users, administrators, CRM contacts and form submissions) is replaced with a reserved address that can never receive mail, the same person always getting the same one. Every email, SMS and API call notification on the copy is held, and the load refuses to start if the hold is off or a real address is left. Live customer sites are no longer among the sites the release check and the nightly check copy by default.
  • A list that comes back with a short page part way now keeps reading. When a platform answers one page of a list with fewer rows than asked, but has said more rows remain, the move now asks for the rest instead of stopping with "read 2 of the 251". A page that comes back empty still stops the move, as before.
  • A Webflow form that has no submissions and is on no page is still not rebuilt, but it no longer goes missing without a word. It now shows under Left behind in the plan, the report and Verify, with the reason "no submissions, not on any page". A form with submissions, or on a page, is unchanged.
  • Webflow: forms, galleries and paging on collection pages. A site form on a collection's item pages and list page is now rebuilt in the form builder with hCaptcha, as it is on static pages, and Google's reCAPTCHA script is removed from every page whose forms moved. A multi-image gallery is drawn even when its images carry different alt text on each item, a paged list keeps its "1 / 2" page count so page 2 shows the next items, a hidden list that reads the same on every item page no longer stops a template from being rebuilt, and a link typed into a form message is no longer counted as a file someone sent.
  • Webflow: add a form's CSV export for older submissions its API does not give. Webflow can list more submissions than its API serves (one site: 75 listed, 47 through the API). Transform, Forms now takes the form's export, adds the older ones with their dates, and matches the ones already copied so none lands twice.
  • The check that every page loads nothing from the old site, and that every file it loads answers, now asks four pages and files at a time instead of one at a time, with the same verdict. The staff review also shows when each phase of a run started and ended.
  • The checks never open account action pages. Signing out, password reset and change password, unsubscribe, delete or close account, email confirmation and resend pages are no longer requested on the old site or the new one, signed in or not, and are never photographed. On some sites opening the password reset page while signed in emailed the member a reset link. Each page left out is listed as "not checked: account action page" so the count stays honest.
  • The guide now matches the 0.8.35 to 0.8.38 behavior. The Close and Delete steps say the old site's Insites name can be typed to confirm, the log labels list "Insites cache: not yours", and the Webflow page covers files from a form no page draws and the 404 redirect line on a sync.

November 2, 2026: version 0.8.38

  • A form no page draws any more has its uploaded files copied. Submissions to a Webflow form whose page is gone, such as an old Careers form, used to bring each resume across as Webflow's address, which opens only with a Webflow login, and the SOURCE check then failed every row. Each file is now copied into a file column, as for a form on a page, and SOURCE agrees with what was copied.
  • Release checks now stop in seconds when the Insites v6 Console sign-in they use has lapsed. A daily check warns before it does, so a release is not held up waiting for a person to sign in again.

November 1, 2026: version 0.8.37

  • An automated check of the toast messages no longer fails now and then on a busy machine. It now waits for the page to stop redrawing before it presses a button. Nothing in the tool changed.
  • The old instance is always shown by its Insites name. Emails, problem reports, Activity, the Migrations list and every page use that name. Customer domains and Insites addresses show as they are.
  • A sync no longer keeps a 404 page an earlier move wrote without its redirect line. A move from before the 404 page got the redirect line is no longer mistaken for a change your team made on the new site, so the next sync adds the line and your redirects answer.
  • The new instance's cache starting up is no longer listed as yours to fix. A "Redis is loading the dataset in memory" entry in the new site's log is labeled "Insites cache: not yours", accepted with its reason, and makes no To do job.

November 1, 2026: version 0.8.36

  • A move from Insites v4 now leaves the CRM's Form Submission activities behind, as a move from v5 does, and the To do list names the old instance by its Insites name. Each form submission stays on its contact under Related data, so the activity that only repeated it is not copied; the plan and the run report give the count and the reason. Every other activity is copied. Where the old instance's address was an infrastructure address, To do jobs now call it by the instance's name, for example "the old Insites instance buw-v5".

November 1, 2026: version 0.8.35

  • The nightly review can read one migration's whole history. A new staff-only read lists every event of a run a page at a time, every failed check with the names of the fields that differ (the review now shows these in full), and the tables the plan covers, so a run can be diagnosed after its events scroll out of the short review.
  • A migration that passed its checks no longer gets a "nothing to fix" diagnosis. The automatic diagnosis now reads a problem only when a run failed, paused on a retry, or Verify ended with at least one failed check. Checks that passed, were not measured, or are notes only no longer trigger it.
  • Check again presses are now recorded. Pressing Check again on a code check, or Check everything again, now writes an entry in the run's history, so the nightly review counts them with the other recovery presses.
  • A test that failed now and then no longer does. The check that the Ask box keeps its typing while the browser reloads was timing-dependent and sometimes failed for no real reason. It now waits for what it needs, so a failed build means a real fault.

November 1, 2026: version 0.8.34

  • The Records, read again from the source check no longer fails every row of a form that takes a file. A form with a file upload, such as a careers form asking for a resume, was read again with each file as plain text and compared with the file the new site holds, so every one of its rows was counted as changed on the old site. Each file is now compared by the file the new site holds, and a row whose name, email or file really changed is still reported.
  • Verify no longer counts a reused form table twice. When a move loads a form into a table an earlier move made, such as email_form_2, the Everything the source holds check counts that form once, under the table it landed in. It no longer reports the original table as missing, and the number accounted for can never be more than the total.
  • A page the browser could not paint is photographed again. When the browser answers "Unable to capture screenshot", the page is photographed again after a short pause, then once more at the window's height. Before, the same pages were listed as not photographed on every nightly check. If all three tries fail, Verify says the browser could not paint the page, in place of the browser's own error.
  • The staff review shows which fields differ. For each failed Verify check, the nightly review now lists which fields differ on each row or file, by name only and never with their values, and how many times Carry on, Try again now and Run again were pressed over the whole run. Nothing changes on the migration screens.

November 1, 2026: version 0.8.33

  • v5 databases now show in the v6 Databases screen, with working fields and list columns. Data module and Content Manager tables move to modules/ins_databases/, with the site's code changed to the new names and every row's id and dates kept. Upload, phone, rich text and decimal fields get controls and types v6 accepts, email fields link to their CRM contact, and each table's items list shows its main fields instead of only the ID and dates.
  • A v5 move leaves the CRM's Form Submission activities behind. The v5 CRM logged one activity for every form submission. On v6 a submission is kept on its contact under Related data, so these activities are no longer copied, and a form no longer sends the v5 API call that logged them. The plan and the run report give the count and the reason. Every other activity is still copied.
  • Rollback deletes large batches without timing out, layouts show their SEO tags, and hCaptcha forms are flagged. A rollback now deletes in the background and waits until every row is gone, so a large delete no longer fails with a 504. A layout that captured yield 'seo' and printed it is offered a fix that yields directly, so the SEO tags render instead of showing as text. A form protected by hCaptcha gets a To do job saying not to save it in the Form Builder, which cannot show hCaptcha yet.
  • Release checks no longer fail when the test machine goes to sleep. Nothing changes on screen; releases are checked more reliably.

October 31, 2026: version 0.8.32

  • GitHub is available to everyone. Choose GitHub on the Source step to move a static site from a GitHub repository: its built pages, files, Formspree and Netlify forms and redirects. A public repository needs no token. Moving a site from GitHub.
  • A public GitHub repository needs no token. On the Source step, leave the token empty and the tool reads a public repository the way anyone can, in about six requests to GitHub for a whole site. A private repository still needs a read-only token, and the Source step says so if it is missing. Reading a public repository.
  • The webhook job lists the webhooks to switch back on. Switch webhooks back on after cutover now names each webhook that was on on the old instance, by its event and the host it sends to, and says the others stay off. A move where no webhook was on has no job. Review the pages that differ no longer appears for a page that was not compared, such as one the old site could not answer.
  • Two maintenance workflows load again. Nothing changes on screen.
  • Two more checks on how a migration loads and copies files now give the same answer every time. They no longer fail at random on a busy test machine, so fixes reach you without false alarms holding them up.

October 31, 2026: version 0.8.31

  • When the page stops waiting for an action, it now tells Insites. If an action took longer than the page waits and it probably worked, the tool now tells you to reload and not press it again, and Insites sees which action was slow.
  • The documentation is up to date. GoDaddy now shows as Available, and the guides cover Webflow forms and redirects, waits, run again and the Ask box.
  • Every failed run now keeps its plain cause. The nightly review and the first responder read why a run stopped without opening its log.

October 31, 2026: version 0.8.30

  • A GitHub connection check now refuses every altered link. A small number of tampered sign-in checks could previously be accepted; they are now always refused.
  • Insites staff can review migrations overnight. A read-only, scrubbed summary of open and recent migrations helps Insites spot and fix problems before you report them.

October 31, 2026: version 0.8.29

  • A slow background task no longer holds up the others. The tool's five-minute housekeeping now stops waiting for any one task after 90 seconds, names it, and carries on, so stalled migrations are still picked up again.
  • A site that gains a row while the tool reads it no longer stops the read. When a new item arrived mid-read, the same item could come back on two pages and the read stopped with "read 666 of the 665". The tool now drops the repeat and carries on.

October 31, 2026: version 0.8.28

  • GoDaddy is available to everyone. Choose GoDaddy on the Source step to move a GoDaddy Website Builder site: its pages with their design, menus, images, blog posts, forms and redirects. GoDaddy says what moves and what stays on GoDaddy.
  • Run again starts in seconds, not a minute and a half. The checks it makes before starting now run at the same time, and the key check on an old site counts its contents a few at a time. A key the site refuses is still caught before the run starts.
  • An error that stopped the tool without a message is now logged. Some failures ended a request with a plain server error and left nothing to read. They now write what went wrong, so the cause can be found and fixed.
  • The Ask about this migration box keeps what you type. If the page moved while you were writing a question, the cursor jumped to the step heading and the next words you typed were lost. The cursor now stays in the box.
  • Check for changes and Check again on the new site no longer report a failure that did not happen. When a check took longer than a minute, the page said the tool did not answer even though the check had finished. It now waits for the stored result and shows it.

October 30, 2026: version 0.8.27

  • When a migration fails, pauses or a check fails, the page now says what happened and the one right action. It says whether anything is lost, shows the evidence it used, and no longer offers Carry on when trying again cannot work. It plans a migration again by itself when the plan was made before the fix for its error, and stops trying again when every try would fail the same way. See When something goes wrong.
  • A Webflow form reused from an earlier move keeps its emails' files under the earlier name too. Moving a site again no longer reports the form's autoresponder as missing on the new site.
  • A Webflow collection list that is empty on every page is copied as Webflow shows it. Its "No items found." message is kept on pages built from a template, so those pages read the same as the old site.
  • A site file already on the new site is sent again when it is served as the wrong type. A copy left by an earlier move kept the type it was stored with, so a move skipped it and Verify reported it. Older font types such as application/x-font-woff are accepted, because a browser uses a font whatever its type.
  • A Webflow collection list where some entries leave a field empty now reads its table. Webflow marks an empty field's element with w-dyn-bind-empty, and the tool could not explain that mark, so the whole list moved as fixed HTML: new items did not show, drafts did not hide, and page 2 repeated page 1. Run the move again to rebuild such a list.
  • Webflow moves copy submissions sent through older copies of a form, and their files. Submissions Webflow still holds for a form that was deleted, replaced by a copy, or is no longer on a page now load into the table of the form with the same name, and each one's uploaded file, such as a resume sent in a list of one, is copied into the file column with the others.
  • A Webflow form's file field no longer says "Upload failed" because its column stayed text. When the new site already held the form's file column as text, read back under its older name, the load now replaces it with a file column as it does for any other text column, and a column of any other type is named in the run so it can be fixed before visitors send files.
  • The page-fields check no longer flags a form's own name. A Webflow collection that describes forms, such as "Contact Forms", holds the forms' headings, so the heading on every page was reported as a list that had been copied as fixed text. It is skipped now, and the lists that really were copied still show.
  • The asset files check no longer stalls on a file store that does not answer. A file whose address never answers is tried twice, for up to 20 seconds each, and then named as not answering. It used to wait 2 minutes, three times, and ask three more times, so one hung file could use a whole step and the check stopped with "out of time" three times in a row.
  • A built website with an _astro or _next folder keeps its styles and scripts. The GitHub website source skipped every folder whose name starts with an underscore, so an Astro or Next.js site arrived without its CSS, scripts and images. It now skips only the source folders of Jekyll and Hugo (_layouts, _includes, _posts, _data, _sass) and copies the rest.
  • The Destination step checks every Insites module on the new instance against its latest release. A module behind it reads, for example, "CRM is on v6.1.5, the latest is v6.1.6", with where to update it in Insites Console, and goes on the To do list as one job before cutover. When every module is current, the step says so in one line. Check again, and every plan including the final sync's, reads the versions again. It never stops the migration.
  • Redirects set in Settings now work on a site whose 404 page was copied from the old site. A copied 404 page, such as Webflow's, lacked the line that hands an unmatched address to Settings > Redirects, so every redirect answered 404. The load now adds that line to a copied 404 page that does not have it.

October 30, 2026: version 0.8.26

  • Copy it again, Check this file again, Copy the old site's version again and Accept, with a reason, show their result even when they take more than a minute. The page used to stop waiting after 60 seconds and say the tool did not answer, though the copy, the check or the acceptance had worked. It now keeps reading the migration until what you asked for is there, and shows it. A refusal from the tool still shows at once.
  • A load no longer stalls on the same slow request. When the new site is too slow to answer a lookup, a count or an external-id write, the tool asks again in smaller parts instead of repeating the same request, and pressing Try again now no longer uses up one of the six tries.
  • Run again with the latest fixes opens the new run even when starting it takes more than a minute. The page used to stop waiting after 60 seconds and say the tool did not answer, though the run had started; pressing again could start a second one. It now keeps reading the migration until the run it started is there, and opens it.

October 29, 2026: version 0.8.25

  • Copying a row again now works when its id is taken by another table on the new site, and keeps the row's own external id. Such a row used to be refused with "Type name is mismatched" on every press; it is now copied under a new id, once, and the next checks and nightly syncs find it there. A row copied again at its own id no longer loses its external id, so it no longer fails the rows check after it said it matched.
  • Insites v4 pages keep their SEO tags on v6. v4 pages print their title, description, canonical, robots and Open Graph tags through the site manager's SEO partial, which v6 does not have. The move now adds a small partial to the site's own code that prints the same tags from the same page settings, and points each call at it, so those pages open without an error and search engines see what they saw before. The new site's log no longer lists the tool's own lookup of the instance's tables as an error for you to fix.
  • A sync never writes over code changed on the new site. The nightly sync and the final sync leave a page, partial, notification, form or other code file as the new site has it when someone changed it there after the migration last copied it, list it in the report, and add a To do to review whether the old site's later change is also needed. Files the old site added, and files nobody changed on the new site, still copy.
  • Insites v4 sites move more of their code and files, and say plainly what still needs a developer. Form emails that used v4's email layouts are copied and attached to their forms, a v4 page that does not redirect is copied, code that names v4's dropdown values reads v6's, images in v4's old image store and files on another old instance's storage are copied and their links follow them, and an asset the old instance lists at an out-of-date size is checked against what its storage actually serves. Calls to v4 modules v6 does not have, and code reading empty payment keys, are a To do job rather than an unexplained error.
  • A page the new site's network edge could not reach is asked again, not reported as different. When an address answered 520 to 524, meaning the edge in front of the instance could not reach it for a moment, the Pages check compared that answer with the old site's and failed. It is now asked again, and an address still unreachable after that is said as not compared rather than as a page that answers differently.
  • A site whose code takes payments now gets the To do job for its payment keys, even when the old site holds none. Until now the job to add the client's own payment keys was made only from keys the old site held with a value. A site whose code reads them anyway, such as one using the ecommerce module's Stripe payments, had no job, so the error that code writes on the new site was reported as yours to fix. The job now names the code that reads the keys, and the new site's log accepts that error under the job until it is marked done.
  • Running a Webflow move again keeps a form an earlier move numbered. When the first move named a form email_form_2 and a later read named it email_form, Run again saved to a form the new site did not have while the copied page still called the earlier one, so the page showed a Liquid error. The form, its table and every page that shows it now keep the numbered name the new site already has.
  • Insites v4 moves no longer fail checks for problems a To do job already covers. A v4 redirect page that stored its code as 0 is now copied as a redirect instead of being refused. A page whose only difference on the new site is an error a To do job sets right, such as code that uses a part of Insites v4 that v6 does not have, is now accepted on Pages with that job named, as the new site's log already accepts it. And a canonical or Open Graph address that names the site's own domain on both sites is no longer reported as changed to the same value.
  • A Webflow move onto a site that already holds a form table from an earlier move no longer stops at Analyze. The dry run failed with "Something went wrong inside the tool" when the form's submissions were reused under the earlier table name; they now carry that name and the dry run finishes.
  • A code check you have fully dealt with no longer stays under Things that need you. Once every differing code file is kept as the new site has it, the card, its "Needs you" count and its failed fix suggestion are gone.
  • The Upload File button on a migrated Webflow form opens the file picker again, and a re-run turns an old text resume column into a file column. Webflow's script no longer cancels the click on the upload block. When an earlier migration left a file field as a text column of file addresses, the plan now says the load will replace it with an upload column and copy each past file into it, and stops, naming the rows, if any row holds other text.

October 29, 2026: version 0.8.24

  • Beta connectors are open to everyone. A connector in beta, such as GoDaddy, can now be chosen by anyone, marked Beta on the landing page, the Source stage and the connect step. A line on the connect step says what beta means: the connector is new and tested on sample sites, and Report a problem is the way to tell us if something looks wrong.
  • A static site in a GitHub repository can be migrated, in beta. The tool reads the repository through GitHub's API with a fine-grained token that can only read that one repository, and copies the built site: a gh-pages branch, or a committed build folder from Jekyll, Hugo, Eleventy, Astro or a Next.js static export. Every page and file moves, links are pointed at their copies, Formspree and Netlify forms are rebuilt in the Insites form builder, and redirects are read from _redirects, netlify.toml, vercel.json and Jekyll and Hugo redirect pages. Workflows, serverless functions and secrets stay behind, and the plan lists each. It is offered where Insites switches it on.
  • Send to GitHub is coming soon. Your site's code will connect to GitHub through Insites Console. For now the Send to GitHub step is greyed out, a migration can be verified and finished without it, and sends already made still show.
  • Wix sites can migrate to Insites v6, in beta. Connect with an API key and the site ID: every published page with its design, the blog, CMS collections, forms with their past submissions, contacts and members, media and redirects move. A Wix store, bookings, events, other Wix apps and Velo code stay on Wix, and the plan names them.
  • GoDaddy Website Builder sites can be migrated, in beta. The tool reads the published site, with no API key needed: every page with its design, menus, blog posts and files, its forms rebuilt in the Insites form builder, redirects, and past form messages from a file you add. The online store and contacts stay on GoDaddy, and the plan lists each. It is open to everyone, marked Beta.
  • The new site's log check no longer blames you when the instance's database connection drops. A one-off database connection error with no page or file named is listed as Insites's own and accepted with its reason, so it no longer fails LOGS or adds a To do job you cannot do.

October 28, 2026: version 0.8.23

  • The one-off "Move the site's files into Assets" action is gone, and any agency can now use its own custom Teamwork domain. Sites moved before version 0.8.6 no longer show the move on the Close step. A custom Teamwork domain such as pm.youragency.com works with nothing to ask Insites for: the tool checks that its DNS points to Teamwork, as Teamwork's custom domain setup asks, before sending your key. An address that only looks like Teamwork is refused.
  • Run again with the latest fixes. After a release, a migration that has loaded can be run again on the new version, onto the same new instance, from Verify's Result or the Launch timeline. The saved Transform settings, the load options, the accepted items, the To do ticks and the cutover steps are carried, so you do not go through Transform again. The old site is read again and the plan comes first. Rows already copied are brought up to date where they are, never copied twice, and rows changed on the new site since the load are kept as they are there. The nightly sync stops while it runs. A run again that failed, was stopped or was never confirmed does not stop the migration being run again. No need to start a new migration to pick up a fix.
  • Redirects now go to Settings > Redirects on the new instance. Each redirect is written to Settings > Redirects in the new instance's admin, so you can see and change it there after the move: the ones you paste, the ones the old site keeps, the ones the tool adds when a page's address changes, and an Insites instance's own redirect pages that name one exact address. A wildcard redirect, which that screen cannot hold, is still written as a page that redirects. While redirects added on that screen do not yet answer visitors, each one is also written as a page that redirects, so every old address keeps working; the REDIRECTS check and Old addresses redirect prove each answers with one hop. An old address already on the new instance's Settings > Redirects is left as it is and listed on the plan with its target. The plan warns when the 404 page does not include the line that makes those redirects answer. A rollback leaves in place any redirect someone changed on that screen after the move.
  • The 14-day watch can file what it finds as Teamwork tasks. Choose a Teamwork project, task list and assignee on the Watch step, before or during the watch, and each problem on your site becomes one task, with a comment when it is seen again or seen fixed. The watch emails link each task, and say so when one could not be filed.
  • Move the domain now warns about Console's "Domain couldn't connect" email. If you add the domain in Console before its DNS points at the new site, Insites emails you that the domain failed to connect. The job on Cutover now says this is expected until the DNS has moved, names your domain, and says you do not need to email support.
  • Starting the 14-day watch says you can leave the page. While it starts, the message says you can leave the page because the watch runs on the tool, and once it has started it says the first look and the first email come within about 5 minutes. Other actions that carry on by themselves, such as the final sync and the checks, say the same while they start. A domain job ticked before the domain has moved now reads as expected, not as an error.
  • A large send to GitHub no longer fails at the time limit. The send now runs in steps: files already sent are kept on GitHub, each step carries on from where the last stopped, and nothing is committed until every file is in. If you leave the page part way, press Carry on sending when you come back.
  • Find out more on a To do job answers in seconds, and is often ready before you press it. When After cutover opens, the tool explains every open job in one call, so each Find out more shows its answer straight away. A job explained on its own now takes about 2 seconds of AI time instead of 3 or more, and the tool saves the answer in one step rather than three. An answer is kept on its job and shown again whenever the page opens, and the tool asks again only when the job's own words change.
  • Buttons on a migration answer faster in an account with many migrations. Most actions on a migration, such as saving a setting, accepting an item, checking the new site or starting a final sync, no longer read every migration in the account before they answer. They read only the migration they act on. Rolling back, starting a final sync and turning on the nightly sync each read the account once instead of two or three times.
  • A Webflow form's file upload now sends the file only to Insites, and Webflow's empty-image placeholder no longer stays on your pages. Webflow's own script used to pick up a migrated upload field too, send the file to Webflow and show it as uploaded while Insites never got it. The tool now takes the field away from that script, so the file goes to the form's upload column on Insites and the form can be sent. Where a page used Webflow's placeholder for an empty image (an address on cdn.prod.website-files.com that Webflow refuses to everyone), the page now draws an empty image in its place, whether or not you chose to replace Webflow's file addresses.
  • A page that could not be checked no longer fails a test account. On Verify, Things that need you, a test account whose pages all matched except ones the old site did not answer (a page that returns 503, for example) now reads "Signed in. 23 of 24 pages match; 1 could not be checked" and names the page. It no longer shows "Signed-in check failed" or "1 page differs", it does not appear under Things that need you, and it no longer asks you to fix the email or password. Only pages that really answer differently count as differing.
  • A test account that signed in no longer reads as a failed sign-in. On Verify, Things that need you, a test account whose sign-in worked but whose pages differ now says "Signed in. 1 page differs" and names the page. "Could not sign in" appears only when sign-in failed, and only then does the tool ask you to fix the email, password or sign-in page.
  • The site's own files check asks again before calling a file missing. A file the destination lists but its file storage misses once is asked up to three more times, so a short storage delay no longer fails a verified migration.

October 28, 2026: version 0.8.22

  • Acronyms keep their capitals in the Verify headings. A check about SEO tags now reads "Not proved yet: SEO tags" instead of "Not proved yet: sEO tags". The same applies to URL, DNS, CRM, API and PDF.
  • Removing a test account on Verify, Things that need you, no longer leaves the page saying nothing needs you. It says which account you removed and that its signed-in check went with it, and offers the form to add a test account right there. An account added on Verify is checked on both sites straight away, without running the whole verification again. Plan, Signed-in checks now points to Verify once the load has run.

October 27, 2026: version 0.8.21

  • Clear and Stop watching buttons are now red outlines. Every Clear button (filters, lists, your choices, and Clear all on notifications) and Stop watching now have a red outline, so you can see they remove or stop something. Undo stays plain.
  • Starting a load shows its checks as a list, and starts sooner. After you type the plan code and press Load, the Loading card used to show one line, "Starting the load...", for about ten seconds. It now lists the steps: checking the plan code and both keys, starting the load, then writing to the new instance. Each line shows a spinner while it runs and a tick when the tool says it is done, so a slow check stays on its spinner rather than ticking early. The wait is also shorter: the check that no other migration is loading the same instance used to read every migration the tool holds, and now reads only the ones that are loading, checking or rolling back.
  • Saving a box on Plan, What the load carries, is faster on a workspace with many migrations. The tool saved the box only after reading every migration in the workspace; it now reads just the one you are on.
  • Marking a cutover step done, or ticking a job on Launch, saves in about two seconds instead of about twenty. The step or job shows as saved as soon as the tool has saved it, and the rest of the migration refreshes behind it. Switching off a nightly sync kept on another run of the migration now happens just after the save, and the nightly sync also refuses to run on any migration whose cutover has started.
  • Count the changes again, Check for changes and Run the final sync again now answer the moment you press them. The button shows a spinner and says Counting, Checking or Starting, and a status block appears at once in the card saying what it is doing, that nothing is written to either site, how long it usually takes for a site this size, and that you can leave the page. The card keeps its layout from the press to the result, and the result replaces the status in place with a short line such as "Counted: 72 new, 2 changed, 6 deleted." The page updates by itself when the count is done. The progress line now reads "Comparing with what the load copied: 15,464 of 15,464 records", and it no longer shows figures left over from the load. The final sync's Load now shows what it is really doing, step by step (reading the old site's code and translations, copying the code, with counts), and a sync with no record changes says so before you press Load: "Load still copies the site's code and translation files."
  • The progress bar on the Launch pages now has After cutover, with its own count. It shows the same steps as the list down the side and the launch timeline: Before cutover, Cutover, After cutover, Watch and Close. On After cutover the bar now marks After cutover as where you are, and Watch counts only the watch, so it no longer says "1 of 4 done" for your After cutover jobs.
  • Every button that deletes, removes, rolls back, disconnects or stops is now red. On the Close page, Delete the migration and Undo this load each have their own heading and a warning that they cannot be undone, and Undo this load is no longer folded away. The same red is used for Roll back and Delete on a stopped or failed migration, Remove the keys, Remove the old copies, Remove for a member or test account, Disconnect from GitHub and Stop. Red buttons now show a red focus ring and shadow instead of a blue one.
  • Closing a migration answers in seconds, however many runs it has. The keys are removed and every run of the migration is closed before the dialog closes, and the page shows the migration as closed as soon as the tool answers, reading it again behind that. The copies of the old site are removed just after. Until now, on a migration with many large runs, Close could take over a minute, and the page said the tool had not answered even though it went on to close. Pressing Close again on a closed migration shows it as closed.
  • Send to GitHub now leaves out a file you accepted as missing on Verify. It no longer stops on a file you already accepted (for example one that was unused and only on the old site). The send log says which file it left out, who accepted it and why. A missing file nobody accepted still stops the send.
  • Verify no longer passes translations that were never copied. A migration that loaded before translations were copied, or whose old site's export held no translation files, used to pass the Translations check with nothing copied. Verify now says "Translations were not copied on this run" and asks you to run a final sync, or names how many translation keys the code uses that the export did not hold, and the To do list carries a job for it. Module translations (modules/*/public/translations) are still deliberately not copied.
  • The GitHub repository list shows who can see each repository. On Destination, GitHub, every repository now says (private), (public) or (internal) with a padlock, globe or building icon, and the chosen repository keeps its icon and label. Create a new repository stands out with a plus icon and the app's blue, and stays at the top while you search. The status beside Save this choice now lines up with the button.
  • Pages and code now says which code reads the old SEO keys, and which choice to make. For an Insites v5 site, the Old SEO keys section lists, for each key v6 never reads, the places in the site's code that read it, or says that nothing does. It recommends keeping the keys (the default), because nothing breaks and their values reach v6's settings either way. When nothing reads them, it says ticking is safe too. The tick box now explains what it removes.
  • The Launch timeline table now has a Close row, and the current step stands out in purple. Under the timeline, the table of what each step does lists Close after Watch: what closing ends (the checks, copies and syncs, the watch and the nightly sync), that the keys are removed, that the report and every decision are kept, and that an owner can reopen it. The row says Now when Close is the step you are on. The You are here and Now marks are purple, the same purple as Agency in the account menu, so they are easy to see.
  • Transform now names the domains on a Webflow site. Where it said "Domains 2", it now lists them, each with what the source says it is, and shows the first three with "and N more" when there are more. The report lists them too.
  • Transform now says which step you changed, and Undo all says what it will undo. A step shows only its own changes, such as "You changed 2 settings on this step. Undo them", and nothing when it has none, so Advanced no longer shows a count and an Undo all when it has no changes of its own. Analyze names the steps you changed, each a link, with Undo all. Undo all lists what it will remove, step by step with counts, before it asks you to confirm, and each step can be undone on its own while the others stay as they are.
  • The module versions table on Destination now has three columns. Module, Code name and Installed version each get their own column, sized to what it holds, so the version sits next to the module instead of far across the page.
  • The Redirects step no longer says "none" when it only guessed. Webflow (outside Enterprise), Squarespace and WordPress do not share their redirects with the tool, which can only ask the live site about old addresses. When that finds nothing, the step now says it is not confirmed, in amber, with the steps to export the site's own list from that platform. It stays on the To do list until you add the export or tick "This site has no redirects" with a reason, which goes in the report. It does not stop the load. An added export shows its own count, with the live-site check kept as supporting information. A source whose API lists its redirects, such as an Insites instance or Webflow Enterprise, still says "none" with confidence. How redirects are found.
  • What it holds shows one loading block. While the tool checks the old site and reads what the source holds, the screen now shows one list with a line for each, a spinner while it works, a tick when it is done and a warning if it could not finish. The repeated "Checking the old site" text, the disabled button, the empty bar and the second spinner are gone, the button comes back as Check the old site again once the check has run, and the moving dots after a word no longer shift the text. This applies to every source.
  • The "Sends each one to" box on Forms now explains itself. It says you can add up to 20 addresses separated by commas, points out any entry that is not an email address as you type, and shows how many addresses it will send to.
  • Suggestions for new databases arrive faster. On Transform, Databases, the tool now saves finished suggestions a few at a time rather than one by one, so a migration with many new databases gets its suggested names, groups and tooltips sooner. Nothing finished is lost if the work stops part way.
  • The Transform steps now say clearly whether your choices are saved. The line beside Next shows Unsaved changes, Saving... with a spinner, All changes saved with a check (then Saved with the time), or Not saved with the reason and Retry. It no longer says Saving all the time: a choice the plan could not use yet was being sent again on every refresh. Pressing Next while a save is on its way waits for it, says Saving your changes... on the button, then moves on; if the save fails you stay on the step.
  • Checking a site with thousands of asset files no longer runs out of time. The check of asset files now asks about several files at once, saves how far it got, and carries on in the next step from there instead of starting again from the first file. A step that gets further is counted as progress, so the check is never stopped for getting nowhere while it is still moving.
  • A long load now says about how long it has left, or that it has stopped moving. While a load runs, the Loading page says about how long the part in hand and the whole load have left, worked out from how fast the load has actually gone in its recent steps, and it keeps the estimate when you reload the page. Before there is enough to measure it says it is working it out. If nothing has moved for 30 minutes, it says so plainly and asks you to press Report a problem if that stays.
  • Errors now say what the other service said. When GitHub, the AI service, the photo service, Teamwork, a form service or an instance refuses a request, the error on screen now gives that service's own reason in one line, for example "GitHub said: HTTP 422: name already exists on this account", instead of only a status code. Keys, tokens and email addresses are always taken out first.
  • The docs read more evenly, and no diagram text is cut off. The section headings in the docs menu (Start here, Connectors, How-to guides and the rest) are dark and semibold, and the Insites item under Connectors reads Insites v5, to match Insites v4. It opens a new Insites v5 connector page, beside the v4 page, that says what the tool needs to connect, what it copies and what stays behind. The connectors list and the Overview link to it too. Every diagram now wraps its text inside its box, such as the Load and Launch steps on the Overview, and sits at the left edge of the text. Paragraphs, lists, notes and diagrams share one width and one left edge on every docs page, and every note and warning looks the same.
  • A long wait now shows its result on the open page, even when the connection drops on the way back. If the tool finished a question to AI, Find out more, Suggest a fix, a forms review, Send to GitHub, starting a migration, or a load, check or plan, but the answer was cut off by the network or a time limit in between, the page now reads what the tool stored and shows it, without a refresh. It also checks again the moment you come back to a tab that was in the background.
  • Every button now answers when you press it. The button shows it is working at once, a message says "Working on it" when an action takes more than a moment, and a message then says in plain words what happened, or why it did not and how to try again. The Stop button at the top of a migration now says what it stops, with a tooltip that explains what happens.
  • Suggested names, groups and tooltips for new databases now show as soon as they are ready, and are applied without a click. On Transform, Databases, the open page now checks the migration for finished suggestions while it waits, so they appear without reloading the page. They are applied as they arrive: you can press Next and the plan and load use them. Change any of them, or choose Don't use any. If they take longer than five minutes, the page says so and offers Try again, and suggestions never hold Next.
  • A tick on the Plan page now shows the moment you click it. On What the load carries (the hold on emails, the code and files, the settings and keys), on the Users passwords switch and on the Fixes switches, the box ticks at once, "Saving..." with a spinner sits beside it, and only that box is held until it is saved, so a second click cannot switch it back. A save that fails puts the box back and shows the message with Retry.
  • Sending to GitHub no longer stops on a large repository when GitHub is slow to answer which files it deleted. The tool now asks in smaller batches, then one file at a time, so files the repository deleted on purpose are still left out. If GitHub still cannot answer, the send stops and says why, and nothing is written.

October 27, 2026: version 0.8.20

  • The People page copy button is now an icon, and pages no longer flash the wrong account. The Copy button next to the workspace ID is a small copy icon with a name that shows after half a second. On a phone, each person is a card with the email on its own line and the role beneath it. People, Activity, Settings and Migrations also wait a moment for your account instead of first showing your Personal account and then switching to your agency.
  • A long load of people's details no longer looks stuck, and moves faster. Each step that finishes people's details now counts as progress, so a load that keeps moving is never stopped for getting nowhere. Each step also reads and writes people's details a hundred at a time, instead of reading everyone left before writing anyone, so it no longer reads the same people again on every step.
  • Leave the field out now settles a field whose type differs on the new site. When a field is one type on the old site and another on the new one, choosing Leave the field out and pressing Apply now removes the decision from the plan. The field is not copied, and the report counts the values left behind. Before this fix, the same decision came back after Apply and the load stayed blocked.
  • Copy again on files no longer fails when it runs out of time. A long list of files can take more than one step to copy. Copy again used to stop with an error saying it had paused, even though the files it had copied were fine. It now keeps those files, says how many are left, and carries on with the rest until none are.
  • A Squarespace newsletter sign-up no longer fails Verify. The Form fields check now finds the first name, last name and email on the rebuilt newsletter form, so a Squarespace site with a newsletter block is no longer rolled back for fields it did keep.

October 27, 2026: version 0.8.19

  • A page that never stops loading is now photographed anyway. The Verify step used to fail a page picture when the page kept making requests in the background (a chat widget, a tracker, a live feed). It now waits up to 10 seconds for it to settle and photographs it as it is.
  • Webflow: images in a collection list keep their smaller versions for phones on every page of the list. A card shown only on page 2 or later of a paginated list used to print its image at full size only, because the move read page 1 alone. The move now reads every later page of each paginated list, so each card offers the same srcset and sizes it has on Webflow, and the Verify check "Smaller images for phones" counts the later pages too, so a card that loses them is caught.
  • A page picture is no longer lost when the browser restarts under it. If the browser that photographs your pages closed part-way through a page, the second try was given only the time that was left and often failed. It now gets a full page's time, so fewer pages read as "could not be photographed" on the Verify step.

October 27, 2026: version 0.8.18

  • WordPress is available to everyone. Choose WordPress site on the Source step to move a WordPress site, with an Application Password or the site's export file. What moves from WordPress lists every feature and what happens to it.
  • A WordPress site can be connected with its export file. A site that cannot make an Application Password, such as a free WordPress.com site, connects with the file from Tools, Export, All content. Its posts, terms, comments, menus and media come from the file, and its pages from the live site.
  • A WordPress post's page says its own SEO title, description and address. Yoast SEO's title and description move with each post, and the collection page's layout prints them per post. Rank Math's redirects export and the Redirection plugin's CSV are read correctly, Gravity Forms entries are read through its REST API, and the To do list adds email sending when a mail plugin sent the site's email.
  • A WordPress site's taxonomies, custom fields, comments and menus are copied. Each taxonomy becomes a table of its terms, each Advanced Custom Fields field shown in the REST API becomes a column, approved and waiting comments become a Comments table, and each menu's links become a Menu items table.
  • The SEO check no longer fails an image the move copied, or a staging instance's noindex. An image tag that now names the new site's copy of the same file counts as the same, and on a staging instance a robots tag that says noindex is listed, not counted. A tag that really changed still fails.
  • WordPress sites can be connected, in beta. Connect with an Administrator's Application Password to see what the site holds and run a dry run. If the password is refused, the test says why: a wrong password, no such user, or Application Passwords switched off. Sites with Plain permalinks work too.
  • Move again no longer points links at the first new instance. A replacement that sent the old site's file or instance address to the first new instance stays behind, is listed under Not carried, and the plan offers it again with the new instance's address. Before, a move from staging to production could point links at the staging instance's files.
  • A website's file host is no longer swapped for the new instance's. For a Webflow or Squarespace site, the Plan step no longer offers to replace the site's file host with the new instance's file address. Every file the move copies already points at its copy, so the swap only broke what was left, such as Webflow's own empty-image placeholder, which then failed the Addresses check.
  • The nightly sync waits for you only about edits it would undo. A row someone changed on the new site stops the night only when the old site changed it too, because only then would the sync copy over that edit. Before, any edit on the new site stopped every night, even when nothing on the old site had changed.
  • A nightly or final sync no longer reports rows as missing when the first load gave them a new id. The Records check finds each row where the first load put it, so a sync that changed nothing reads as matching instead of listing rows that are on the new site.
  • Sign-in and access are tighter. A sign-in link now finishes only in the browser that opened it, and the button in a migration email signs you in for one hour rather than 30 days; ask for a link on the sign-in page to stay signed in longer. Sign-in links, invitations and migration emails now go to you alone, with no copy kept by Insites. Someone an agency invites can run one migration at a time in their own Personal account until Insites approves it, as anyone new can. Live updates on a migration's page refresh their access every hour, and the approval page no longer says whether a sign-up exists.

October 27, 2026: version 0.8.17

  • Problems are easier to find and fix. The Migration Tool team can now see which version of the page a problem happened on, and when a request fails or the page cannot connect, it is noted for the team with what the page was doing and the error number. Nothing you typed, no key, and no page content is included.
  • Copy again works by why the items failed. On Verify, a problem whose items failed for more than one reason lists them by reason, such as files not on the new site and files served as the wrong kind, each with its own Copy these again, so you copy only the ones that copying fixes.
  • A sync's Verify says what changed since the last sync. After a final sync or a nightly sync, Result says how many checks changed since the run before, and each is marked Changed since the last sync, with the items that fail now and did not then. When nothing changed, it says so.
  • A long load shows its progress in the browser tab. The tab's title says how far the load has got, such as "42% loaded", then "Done" or "Needs you". Press Also tell me in this browser to have the browser tell you when it finishes or needs you while you are on another tab. You can still close the page: the load carries on, and the emails come as before.
  • The migrations list says how many things each migration needs you for. Under its status, a migration that is waiting for a person shows Needs you with a count: decisions on its plan, Things that need you on Verify not yet dealt with, and To do jobs not yet done. Pointing at it says which.
  • Roll back, Close, Delete and Plan it again ask you to type the site's address. Roll back asks for the new site's address, and the others for the old site's, so you look at which site it is before anything happens. Each asks on the page, and the address shows in the dialog to copy.
  • Every check that did not pass links to its explanation. On Verify, each check that failed, and each thing that needs you, has a Why did this fail? link to that check in the docs: what it compares, when it passes and what it is first tried on.
  • Verify checks the forms staff used to test one by one. Form fields says when a field the old form asked for, a file upload included, is missing from the new form or posts nowhere; Forms add CRM contacts says when a rebuilt form makes no CRM contact, or one without the name, email or phone it asks for; Files sent through forms says when a file people sent before the move, such as a resume, does not open on the new site.
  • Verify measures form spacing and phone width on both sites. Form spacing reads each page whose form has a captcha at a desktop and a phone width and says when the space above Submit, or the captcha's size, moved by more than 8 pixels. Pages on a phone says when a page runs off the side of a phone where the old site fit.
  • Verify checks every page's links and tracking tags. Links on every page says when a link to the site's own pages does not open on the new site, leaving out links that fail on the old site too. Analytics and tracking tags says when a Google Analytics, Tag Manager, Meta pixel or other tracking id the old page loads is missing from the new page.
  • Verify says when a page shows a collection field as fixed text. Fields that change the page names each field the old page shows that the new page writes in as text, and each list copied as fixed HTML, so an edit in the admin would not reach the page. Webflow page ids says when a moved page carries another page's id, which can keep a hero hidden.
  • Clearer stage screens. GitHub is listed as a source, coming soon, on the home page and the Source step, with its own waitlist. Destination's What it holds lists the version of each Insites module the new instance has; whether a version is the latest is checked in Insites Console. On Destination's GitHub step, Change is now Change repository, and Do not send to GitHub is a red outlined button. Every Transform step is titled with its own name while it waits or loads, never just "Transform". Verify's Result opens with two figures, each saying what it counts: the records copied, out of the records on the old site, and the items checked that passed, out of every item checked, and no longer repeats them in a sentence or points at Send to GitHub, which is the next step anyway. On the Launch timeline, the circle of the step you are on pulses, unless your system is set to reduce motion.
  • A tidier menu and home page, and clearer messages when the page cannot connect. When the page cannot reach the tool, a message at the top right now says whether your device looks offline or the Migration Tool server had a problem, and what the page was doing, with Retry, Report a problem and a close button, in place of "Failed to fetch" across the page. Messages sit at the top right on a computer, clear of every page's buttons, and at the bottom on a phone. Tooltips on statuses show after half a second. In the menu, the logo is larger with no words under it, the collapsed menu's logo is smaller, Migrations sits a little lower, a divider separates Change Log from your name, and an agency is marked by the word Agency in purple rather than a shaded box. Settings has a heading over the app versions and a divider between each setting. The home page has a top bar of its own, with Sign in, or Go to dashboard when you are signed in, and no app menu.
  • A migration nobody has opened for 90 days no longer keeps its keys. The person who started it is emailed 14 days before the two keys are removed, and opening the migration keeps them. The migration, its report and every decision stay, and you can give it a new key when you need one. Settings you change while a step is running, such as whether passwords are copied, are now kept rather than replaced by the step's own copy, and two owners can no longer remove or demote each other at the same moment and leave an agency with none.
  • A Webflow form's file upload field moves with the form. It uploads to the form's table on Insites with the size limit and file types Webflow gave it, kept private for the site's administrators, and the files people sent on Webflow are copied with the site's token. A file Webflow will not hand over is named by its row. A site moved before this, whose form table keeps each file as a Webflow address, has that column made a file column on its next load or sync, so the files are copied into it.
  • The captcha on a moved Webflow form keeps Webflow's gap above the button and loads only when needed. It sits where Webflow's did, is shrunk on small screens the way the site shrank its reCAPTCHA, and its script loads once a visitor reaches for the form, so pages load faster. The old site's reCAPTCHA script is also taken out when a form only styles it.
  • New Webflow form submissions save the same way the copied ones do. Each gets its Sent date, tick boxes save true or false, and whole numbers show without ".0" on the page.
  • Hold emails and outside connections says exactly what it holds. The option and the Launch note no longer say a test submission reaches nobody. They say what is held (the site's own email, SMS and API call notifications, and the sends its code makes by name), that anything triggered while held is skipped and never sent later, and what is not held: sends written out in full in the code, emails the new instance's modules and platform send, forms embedded from other services, and scripts that post to other sites. The plan now also names, under Not held, sends in SMS and API call notifications and their callbacks, in authorization policies, code that sends through one of the new instance's modules, and each form from another service on the pages. Payment keys are described as they are handled: constants for known providers, such as Stripe and PayPal, are not copied. See Test on a live instance safely.
  • What moves from Webflow, feature by feature. A new docs page, What moves from Webflow, lists every Webflow feature: CMS fields, collection list settings, images and video, interactions, forms, languages, the shop and site settings, with what moves, what moves in part, and what to do about what does not.
  • A closed migration stays closed as it was. Pressing Close again no longer changes who closed it or when, and a closed migration no longer takes new or changed test accounts, so no password is kept after closing.
  • A go-ahead with checks failing now covers only the checks that were failing when you gave it. If a different check starts failing afterwards, the tool asks you again, by name, before the final sync or the domain move goes live.
  • Emails and outside connections wait for a working run before turning on at the domain step. When the domain step is marked done while a sync is still loading, they stay held and Cutover says why, as the Turn on button already did.
  • A mistyped address is now said plainly. A key whose address is not a real web address, or a link with a broken character in it, gets a short message instead of an internal error, and a docs link with a broken ending no longer stops search from loading.
  • Translations now move from Insites v5 and v6. The site's translation files, in every language, are copied to the new instance and merged with any it already has, so pages that use translated text show their words, not translation names. A new check, Translations, confirms it, and the To do list no longer asks you to deploy them with the Insites CLI.
  • A collection list field stays editable when every item holds the same value. On a Webflow site whose list items all share one heading or one block of rich text, the moved page now prints it from the field, so editing it in the admin changes the site instead of leaving fixed text.
  • Send to GitHub no longer adds back files the repository deleted. When the code goes to an existing repository, a file the repository once had and later deleted on purpose is left out and listed with the date and commit that deleted it, and you can tick it to send it anyway.
  • Webflow moves keep each form, its submissions and a post page's related articles together. A form with a field whose name starts with a number now loads instead of being refused; a form read again after an earlier release saves to the table holding its submissions, and the recheck of the source looks for them there; a "related articles" list that shows the same category without the post itself is rebuilt from the data instead of left empty; and a link to another Webflow site, such as Webflow's own guide, is no longer reported as an address on the old site.

October 26, 2026: version 0.8.16

  • A Squarespace stylesheet no longer sends the move looking for a file that is not there. An icon drawn inside the stylesheet names its own parts the way a page link does, and the move read that as a file to copy, so the files and links checks failed on every page. Those names are now left as they are.
  • Insites v5 pages keep their SEO on v6. Each page's description, Open Graph and canonical settings are copied into the settings v6 prints, so pages now show their meta description and share tags, and each page gets its own share address instead of the home page's. Switches stored as "true" or "false" text become real switches, every page gets a name in the CMS Pages list, and the old SEO keys v6 never reads are listed on Pages and code with an option to leave them out. Verify gets a new advisory check, SEO tags, that compares every page's tags on the old and new sites.
  • Links to the old site now finds files on any old CDN host, whatever the instance. Each one is pointed at the moved site's own copy when it is the same file, and Check again reads the pages and their settings from the new site, so a link fixed there clears and the check says so.
  • Owners can reopen a closed migration, and Close is only for a live site. Reopen brings later fixes across to a launched site, keeping every decision and the load ledger; Close now refuses until the domain step on Cutover is done, unless an owner closes anyway and says why.
  • Point them at the copies now follows each attachment to its copy, even when the copy is in a new folder. A page's share image or a link to an attached file is matched to its attachment record and pointed at the address the new instance actually serves, so the Links check counts it as present instead of saying it was not carried over.
  • Webflow collection images keep their smaller versions for phones. Every resized copy Webflow serves for a collection image is now copied to the new site and offered through srcset, so phones download small images again, and Verify gets a new advisory check, Smaller images for phones, that flags any page offering fewer than the old site.
  • Webflow collection lists now keep their Previous link on page 2 and later. A paged list shows Previous on every page after the first and Next on every page before the last, with Webflow's own markup and classes. Existing migrations pick this up on their next re-run or nightly sync.
  • A website's files load in steps that carry on where they stopped. Images and files a Webflow or other website source names by address are now fetched one at a time between checks of the step's clock, and each one is kept the moment it lands, so a table with many files finishes over several steps instead of starting again each time and failing the load. A file the new site cannot fetch is tried three times and then reported, rather than slowing every step. The migration's page also stays open if a background read is briefly refused.
  • Links to the old site no longer fails on the stock welcome page. Its icon sits on another instance of the old hosting; when the new instance already ships the same picture, byte for byte, the link is pointed at that copy.

October 26, 2026: version 0.8.15

  • Every long wait now stops, says what happened and offers Try again. A few spinners could still wait with no limit, so a request that never answered left them up for good. Ask about this migration, Find out more on a To do job, Suggest a fix, the forms review and form rebuild on Transform, the push to Teamwork, a report download and the send to GitHub now each have a time limit longer than the tool's own. When it runs out, or the request fails, the spinner stops, a plain sentence says what happened and that it may still be on its way, and a Try again button appears. A send to GitHub that never says it finished stops after 11 minutes instead of spinning. Optional steps never hold Next. On the tool's side, every AI call now has a time limit, a push to Teamwork stops making tasks after four minutes and records what it made, so pushing again adds only the rest, and the lock on the forms AI lasts as long as its work and is always let go.
  • Every deploy is now checked in a real browser before anyone else opens the tool. After each production deploy, and each staging deploy, a check opens the tool the way a person would, confirms it is serving the version that was just released, then signs in with a dedicated test account and opens the Migrations list and a test migration at each stage, without changing anything. If a page shows an error, fails to load something, or comes up blank, the Migration Tool Slack channel hears about it straight away, with the deploy named. The test migration only uses Insites test instances, never customer data.
  • Each release is tried on staging before it goes live. A release now reaches migrate.insites.io only after the same build ran on the staging copy of the tool and real migrations from an Insites v5 site, a Webflow site and a Squarespace site passed there, so faults are caught before you meet them.
  • Change log entries no longer collide between releases being built together. Builders now add one small file per change, and release prep joins them into this page. Nothing changes on screen.

October 26, 2026: version 0.8.14

  • Typing in a field no longer jumps the cursor back to the start. On Transform, choices save by themselves as you type, and each save redraws the page. In an email field, such as "Sends each one to" on Forms, that redraw put the cursor back at the start, so the next letters landed in the wrong place: typing "[email protected]" could end up as "iteshane@ins". The field you are typing in is now kept as it is through a save, with your cursor, your selection and every letter you typed, even ones typed while the save was still on its way. This covers every text, email, number and multi-line field the page redraws.
  • Suggested names and tooltips for new databases can no longer spin forever. On Transform, Databases, "Suggesting names, groups and tooltips..." waited with no limit, so a request that never answered left the spinner up for good. The page now waits at most five minutes. If the suggestions do not arrive, it says what happened, with a Try again button, and the step stays usable: suggestions are optional and never hold Next. If another tab is already asking, the page waits for that answer instead of showing an error. The tool now asks about four databases at once, stops after four minutes, keeps each suggestion as it arrives so asking again carries on from there, and gives any database it did not reach the plain defaults, saying so, with a button to suggest the rest.
  • Users no longer reads "Waiting" while the plan is updated after a choice. Each choice you save on a Transform step updates the plan, which takes two to three minutes, and Users said "Waiting for the people check" for all of that time even though the check it already had was still good. Saving choices on one step after another kept Users at Waiting for as long as you worked. Users now keeps the check it has and stays Ready; only a migration that has no people check yet waits for one, and that turns to Ready by itself when the plan arrives.
  • Starting the load says "Starting the load" once, and the top of the page says Loading. After you type the plan code, the Loading card used to say "Starting the load..." twice, once under the heading and once beside the moving dots, while the status at the top still said "Waiting for you". The line under the heading now says the tool is checking both keys before it writes to the new instance, the moving line says "Starting the load...", and the status says Loading from the moment you press Load. Preparing analysis and Rolling back no longer repeat their own words either.
  • Ticking a To do job now shows which job is saving, and the rest of the page stays usable. Before, ticking a job (or marking a cutover step done) greyed out every button until it saved, so you could not tell what was happening. Now only that row changes: a small spinner takes the place of its checkbox, it says "Saving...", and the row pulses gently. When it saves, the box ticks with a short animation and the row reads "Done" with the time and who did it. If the save fails, the tick goes back and the row says why. You can tick several jobs in a row without waiting. The same applies to Undo on an accepted file or person and to removing a test account. Screen readers hear when a save worked or failed, and with reduced motion on there is no pulse and the spinner turns slowly.
  • Page photos on Verify are taken about twice as fast. The browser that photographs the old and new sites now opens up to four pages at once instead of one at a time. Measured on a 56-page site, twice each way: 3.1 and 5.1 photos a minute before, 7.0 and 8.5 after, with fewer pages left unphotographed (13 of 112 against 29 of 112). If the browser runs short of memory or closes, it finishes the rest one page at a time, so no page is lost.
  • A page that answers the same way on both sites now counts as matching. A page such as /robots.txt that answers 404 on the old site and on the new one used to be listed under "Not confirmed" as "could not be checked", with nothing for you to do about it. It now counts as matching, and the result says it answers 404 on both sites, as before. A page that answers 404 on one site and 200 on the other still fails. The third card on the Verify result now says "could not be checked" when items could not be checked, and "don't match" only for items that really differ. A page whose address already ends in a file extension (robots.txt) is no longer asked for with a second extension (/robots.txt.text).
  • Send to GitHub tidies file paths GitHub refuses. A site whose file storage lists a file at a path such as "modules/Assets/public/assets//og-banner.jpg", or lists a folder as if it were a file, could not be sent: GitHub refused the whole commit with "tree.path contains a malformed path component" and named no file. The tool now sends such a file at the tidied path (here "modules/Assets/public/assets/og-banner.jpg"), leaves out folder entries, which hold nothing, and says both in the send's activity log. A file GitHub would still refuse, for example one with ".." in its path or a line break in its name, stops the send with every such file named and what to do: rename or remove it on the new site, then send again.
  • Send to GitHub can be pressed again after a send that stopped part way into a new repository. A send to a new repository creates it first. If that send then stopped, for example on a file path GitHub refused, pressing Send to GitHub again tried to create the repository a second time, and GitHub refused with "Repository creation failed". The tool now records the repository the moment GitHub creates it, and a later send uses it. A repository of that name the tool created on an earlier try, still holding only its first commit, is used too. A repository of that name the tool did not create is never written to: the send stops, names it, and asks you to choose a different name for the new repository or choose it as an existing repository. The pull request now goes into the repository's real default branch, which GitHub sets when it creates the repository (for example master), and Destination and Verify show that branch once it is known, instead of always saying main.
  • The Launch timeline ticks a phase only when nothing in it is left. A phase or a stage now shows as done only when every job or item in it is done or deliberately dismissed. Where you are is the first phase with something still open: with 6 of 7 Before cutover jobs done, Before cutover is current and Cutover is upcoming, even once a cutover step is marked. Ticking the last job turns the phase done and moves you on at once, without a reload. Under each label, a short count says where it stands, for example "6 of 7 done" or "Not started", and the line between the dots fills only up to where you are. The Launch page you are looking at is drawn bold on the bar. In the step list on the left, Verify no longer shows a tick while Things that need you has an open item: it shows "Needs you: 1" instead.
  • Every screen and email counts the records the same way. New, changed, unchanged, left behind, failed and accepted are now counted once for each migration, and the plan cards, Result, the To do list, Things that need you, the message after you accept an item, and the emails all show those same numbers. Each count says what it is out of, for example "Of 1,250 records on the old site, the load will copy 1,180 new and update 20 changed; 4 are unchanged and 46 are left behind, each with a reason." A final sync counts from the same comparison with the first load that Cutover already shows.
  • People: confirmations are toasts, and the add form is one row. After you change a role, send an invitation or remove someone, People now shows a short message that closes by itself after 5 seconds and is read out by screen readers, instead of green text left on the page. Hovering over it or moving keyboard focus into it holds it open. An invitation that could not be sent stays until you dismiss it. Email, Role and Add now sit on one row on a wide screen and stack on a phone.
  • People no longer has a "Forget my Teamwork key" button. It was on your own row. It stays on Settings, which is where it belongs.
  • Every Transform step now has an icon in its heading. Analyze, Pages and code, Site files, Databases, Forms, CRM, Users, Ecommerce, Events, Locator, Other, Redirects and Advanced each show a small line drawing before their title, the same style, size and color as the steps of the other stages, in the light and dark themes. The drawings are decorative: a screen reader skips them.
  • An email the tool could not send now says so. A sign-in link, an invitation or a migration email with no recipient, or sent from an instance with no sender, used to be reported as sent, because the platform accepts one and then drops it. The tool now refuses it before sending, and a migration email that was not sent shows in the migration's activity log with the reason, for example "not sent (refused: no recipient)". An email the platform does not accept is reported the same way. Every email the tool sends still goes through Insites CRM, so it has a row in the instance's Email Logs.
  • The sidebar collapses on every page, and names each icon. The arrow button at the bottom of the sidebar now collapses it to a row of icons, or opens it again, on every page, in the same place. The tool remembers your choice in this browser, on every page. A migration still opens collapsed until you open the sidebar. With the sidebar collapsed, point at an icon, or move to it with the Tab key, and its name shows beside it. The collapsed sidebar shows the full Insites mark at the top. Migrations has a new icon, two arrows, so it no longer looks like a menu button.
  • The Migrations list shows each migration's old and new address in one column. The old address sits on top and the new one under it after an arrow, each on one line. A long address is cut short, and pointing at it shows it in full. This makes room for the Environment, Kind and Records columns on a laptop screen again, from 1280 pixels wide. A long "Started by" address is cut short the same way.
  • Each list page has one title. Migrations, People, Activity, Settings and Sign-ups no longer repeat the page's name in the bar above it: the bar holds New migration, and the page's own heading names it once.
  • Messages stay until you close them, and wait for you on the migration they are about. A message that reports a result, a warning or an error now stays at the bottom of the screen until you close it with its close button, the Escape key, or Clear all. Before, every message closed itself after six seconds, so the result of something slow was often gone by the time you looked back. Moving to another step keeps it. Leaving the migration and coming back to it shows it again, and when a slow action finishes after you left the page, its result is shown when you come back. Up to 3 show at once, newest on top. A confirmation of something quick that the page also shows, such as "Carrying on from where it stopped.", still closes by itself after 5 seconds.
  • Point them at the copies says what that press did, then what is left. On the Combinate intranet one press fixed 15 links, and a second press 2 minutes later said "Nothing was fixed. 4 of 28 links still do not open", which read as though nothing had ever worked. The message now says, for example, "Copied 15 files and fixed 15 links. 4 of 28 links still do not open", counts every number over the addresses the card counts now, and a press that finds the work already done says when it was done and by whom. It names the buttons that exist, Accept, with a reason on Result and Go ahead anyway on Cutover, with Open Result beside it.
  • Files whose names hold "&" or an apostrophe are copied and checked under their real names. A link in a record's text that names "Logo Design &amp; Rebranding.webp" was asked for with "&amp;" in the name, so the old site refused it and the links check said the file could not be copied. The tool now asks for "Logo Design & Rebranding.webp", which the old site serves. A name with an apostrophe inside double quotes is read whole instead of being cut at its first space. When the old site really does not serve a file, the links card says so beside it, so you know there is nothing to copy and Accept, with a reason is the way on.
  • The confirm button of every dialog shows it is working. Accept on Result's Accept, with a reason, and the confirm button of every other dialog (Go ahead anyway, Remove the keys, Roll back, Stop, Close the migration and the rest), shows a spinner from the moment you press it until the change is on the page, then the dialog closes. If it fails, the dialog stays open with the reason and you can press it again.
  • A Squarespace site's pages are counted as they are read. While the source is read, the tool now reports how many of a Squarespace site's pages it has read, counting the pages an earlier step read, so the read can say "reading the pages, 41 of 120". A count of pages never changes the number of records the read shows.
  • Webflow and Squarespace sites are read step by step, several parts at a time. A website used to be read in one piece, and every Transform step waited for the whole read. Now a Webflow site is read as its collections, form submissions, file library, pages and redirects, and a Squarespace site as its shop, customers, orders, payments, pages and redirects, several at a time and in the order of the Transform steps, as far as each part allows. Analyze says of each part that it will be read, is being read or has been read. Each step opens to look through as soon as its own part has been read and says Ready. This part of your site has been read.; a step still waiting says Waiting for this part of your site to be read. Pages and code opens once the pages have been read, so you can look through every step but Redirects while the redirect search runs. The wizard still only goes forward. When a site asks the tool to slow down, the tool sends nothing until the wait it asked for is over, from any part, and reads fewer parts at a time from then on. A read stopped part way carries on from the first part not read yet, and nothing already read is read again. Insites instances are read as before.
  • The two sites at the top of a migration open in a new tab. The old site and the new instance named in the bar at the top of every migration are now links. Point at one, or reach it with the Tab key, and it turns blue and underlined; press it and the site opens in a new tab, so you can look at it without leaving the migration. A screen reader says it opens in a new tab. The Migrations list is unchanged: pressing anywhere on a row still opens that migration.
  • SendGrid is never on the To do list, on any migration. Insites sets up email sending (SendGrid) on every new instance, so there is nothing for you to set up. A To do list made by an earlier version could still hold a job or a step telling you to set it up again, because the list was kept as it was written. It is now left out wherever the list is shown, copied as text, downloaded as CSV, written to the PDF report or pushed to a project management tool, whatever version made it.

October 26, 2026: version 0.8.13

  • A long step no longer fails as "out of time" while it is still working. On www.insites.io (176 pages), converting the pages after reading them kept the tool busy for minutes without a break. The run looked stopped, so it was started again beside itself, and each restart counted as the time limit stopping it. After three it failed with "out of time in extracting (pages)" even though the read was going fine. Now every step (reading the old site, planning, loading, checking, the page photos) uses one shared clock: it pauses between small pieces of work so the run keeps showing it is working, and it carries on in the next step from what it has kept. A run that goes quiet is started again only once the platform could really have stopped it. Planning keeps what it read from the new site when it runs short of time, and the next step builds the plan from that instead of reading it again. Pressing Rebuild the collection pages or Carry on also no longer starts a second copy of the step in the first few seconds.
  • A Webflow collection page with structured data in its code is rebuilt. A blog post or category page whose head carries structured data (a <script type="application/ld+json"> block filled in from the item's name, address, image and dates) used to stop the rebuild with "code that differs between pages", so every post and category stayed its own static page, even after Rebuild the collection pages. Each value in that code is now matched to the field that prints it, including the item's created, updated and published dates, and the rebuilt template prints it from the row. Code that no field explains still stops the rebuild, with where it is.
  • A step still waiting now lines up with the others in the Transform list. Its status sits under its name, like Ready and Needs you. A step whose plan can no longer arrive, because the migration failed or expired first, shows no status instead of Waiting for good.
  • Removing a test account no longer shows its credentials again before the row goes. Pressing Remove on a test account used to stop the spinner when the server answered, and the row came back with its credentials for a few seconds before it disappeared. The button now stays busy and the row says "Removing..." until the table is drawn without it, and it never comes back. If the removal fails, the row returns with the reason. The same fix is shared: every button that changes a migration (Go ahead anyway, Mark done, Undo, Accept, Send and the rest) stays busy until the refreshed migration is drawn, so the old state never shows again first. Removing a person from an account waits for the refreshed list the same way.
  • Point them at the copies fixes links to files that never reached the new site. On a run loaded before this version, a file whose name holds a space (for example "Google Logo.png") was cut at the space and never copied, so pressing Point them at the copies on Verify found nothing to follow. It now copies each missing file from the old site's storage, reading its whole name, points the links at the copies and checks the links again, on the loaded run with no final sync. The message after it counts the same addresses as the card, for example "Fixed 19 links. All 27 open now", and it shows the success tick only when something was fixed and nothing is left; otherwise it is a warning that says what is left and what to do. A suggested fix no longer sends you back to Transform when the tool has a button that fixes the problem, and when a final sync really is needed it says where: Launch, then Cutover, then Start the final sync.
  • Accept an item on the Result step, and the Launch warnings say what fails. Each item on Result's Not confirmed list has Accept, with a reason: the reason goes in the report, and an accepted item no longer holds back the final sync, as the Cutover warning promised. The list's header counts the same items as the cards, for example "20 items in 2 checks". The Cutover warning names the failing half of each check, for example "19 of 27 do not open". On Before cutover, the links job lists its addresses under their own heading, with whole file names, instead of numbering them as steps, and points at Point them at the copies.
  • Send to GitHub is its own step of Verify, so it is not missed. The send used to be a card at the bottom of Result, under the table of counts. It is now the step right after Result: Result, Send to GitHub, Things that need you, Worth a look, Verification log. The side list says where it stands: Needs you when GitHub is connected and nothing has been sent, Sent with the date once it has, and Not connected when there is no GitHub connection, with a link to Settings on the step. The step holds what the card held: the repository, the branch, the pull request link, the files changed, what the send is doing as it runs, and Send the code to GitHub or Send again. Result keeps one line pointing to it, and Next from Result now says Next: Send to GitHub. A link with step=verify&sub=github opens it. Launch still lets you send again after a final sync.
  • The old word for the first phase is gone from the tool. Version 0.8.11 renamed the first phase to "Copied, not launched yet", but the earlier name was still in the help pages, the glossary, the cutover steps and the checklist. They now say "copy" or "before cutover", and a test fails if the word comes back in anything a person can read.
  • The tool's own tests now reach it the way the live service does. On October 25 the live service refused every Transform edit for a short time because one kind of request was never switched on there, and every test still passed. The tests now send each request through the same entry the live service uses, with the same address rules, headers and size limit, so a request the live service would refuse now fails a test first. Nothing changes in how you use the tool.
  • A final sync copies only what changed, and says so. Every load now keeps a ledger of where it put each record. A final sync or a nightly sync compares the old site with that ledger and says, for example, Will copy 3 new, update 2 changed, 0 deleted on the old site, instead of every record it read. It loads only those, updating each changed record where the first load put it. A migration loaded before this version gets its ledger from the new site on its next sync, and any record the tool cannot find there is listed, never copied without you. A sync that would create more records than are new on the old site stops and says why. Its email gives the same counts, and its decision count matches the page. The card that counted lookup values matched to the new instance's own is now named that way.
  • The final sync happens on Cutover, start to finish. Start the final sync no longer opens a new migration at Transform. Step 2 of Cutover follows it: reading what changed, then the counts, Look through them, the plan code and Load, its progress, and a short check of what it changed, ending with Final sync done. A link to the sync, as in its email, opens Cutover too. A sync planned by an earlier version shows Count the changes again, which counts what changed without writing anything.

October 25, 2026: version 0.8.12

  • The menu is now a sidebar on the left. On Migrations, People, Activity and Settings it shows the Insites Migration Tool logo, the account you are working in (agency name and your role), the menu, then Docs, Change Log and you, with the app version, at the bottom. Each page has a bar at the top with its name and New migration. Inside a migration the sidebar narrows to a row of icons with the Insites mark, so the stages sit beside it; point at an icon to see its name, or press the arrow at the bottom to open the full menu, and the tool remembers your choice in this browser. The bar above a migration reads Migrations / old address to new address. On a phone, Menu at the top opens it. Nothing in it moves while the page loads: the account shows the last one you used in this browser, or a placeholder, until it loads.
  • Transform says when a table an earlier move made is reused, and names it. Since 0.8.11, a Webflow form table an earlier move made as webflow_form_ or webflow_ followed by the form's name is written into again rather than copied twice, but only the activity log said so. Once the plan is built, the row on Databases or Forms now reads Will reuse an existing table with that table's name under Will be copied into, then Reusing during the load and Reused after it.
  • Every page uses the full width. Pages now fill the window with the same 24px side gutter as the top bar, so tables get the most room and stop wrapping. Docs text keeps a readable line length. On a phone, a wide table scrolls inside its own box and the page never scrolls sideways.
  • Each Transform step opens as soon as its part of the source is read. Reading an Insites instance now reads several databases at a time, in the order of the Transform steps, and reads the site's pages, code, people and files first, because Pages and code is the first step. Each step opens as soon as its own databases are read, so you can look through Pages and code, Site files and Databases while the CRM and the rest are still being read. A step opened during the read says Ready to look through, and its choices open once the whole read is done. A step whose part is not read yet says Waiting, and Next waits for it. The wizard still only goes forward. Webflow, Squarespace and Siteglide sites are read as before, and their steps open when the whole read is done.
  • A Webflow blog's post pages and list pages are rebuilt, author and category included. A post that names its author or its category through a reference field used to differ from the next post in a way no field explained, so the blog's collection page was not rebuilt and its post pages were copied as static pages. The post page now prints the author or category it names, and the link to that item's page, from the row the reference points at. A category or author page whose list shows only the posts that name it is rebuilt as a list that keeps exactly those posts, and the plan says so for each list, for example "posts items, the ones whose category names this page's item, newest first, all of them". A migration already on Transform builds its next plan from fresh reads, never from reads an earlier version kept. A site read before this version gets its blog rebuilt with Rebuild the collection pages, below, without reading the whole site again.
  • Rebuild the collection pages of a Webflow site already read. Pages and code on Transform has a Rebuild the collection pages button for a Webflow migration that has been read and not loaded yet. It reads the site's pages again and rebuilds its collection pages and lists with this version of the tool, so a site read by an earlier version gains what this one builds, such as blog post and list pages. Every record, file, form submission and redirect from the earlier read is kept exactly as it was, so it takes minutes rather than a whole new read. The step says Rebuilding the collection pages... at once, the activity log says Rebuilt the collection pages with how many were rebuilt, and the plan is built again, so you type its code again before the load.
  • Settings shows the app and server versions, and "What's new" opens in a new tab. Settings now says, for example, "App version 0.8.12, server version 0.8.12". Both numbers come from the same place, the top heading of this change log. If they differ, Settings says so plainly, for example "The app is 0.8.12 and the server is 0.8.11. Refresh to update." The server version is also in /api/version as version. The "What's new" link in the "new version available" banner opens the change log in a new tab, so you keep your place and can refresh when you are ready.
  • The run bar and the footer line up with the top bar. The bar under the top bar, with the old and new addresses, the status, Report a problem and the close button, now runs the full width of the page with the same side margin as the top bar: the addresses start under the logo and the buttons end under your account. In the footer, Next sits at the far right on the same row as Back, and the stage text and dots stay centered between them. On a phone, nothing scrolls sideways on any stage.

October 25, 2026: version 0.8.11

  • Finalize is now called Launch. The last stage is named for what it does, everywhere in the tool, the docs and the emails. Each Launch step shows a row with where you are: Before cutover, Cutover, Watch and Close. The first phase is now called "Copied, not launched yet" rather than "Rehearse", because the content really has been copied. The Verify result shows three cards at the top (items copied, confirmed, and don't match) instead of a large colored box, and no longer repeats links to Things that need you, Worth a look and the Verification log, which have their own steps. After you type the plan code, the tool moves to Loading at once and says "Starting the load..." while the load starts.
  • The plan no longer asks again what Transform already settled. After choosing item by item on the Transform steps, What the load carries asked again with three broad ticks: Copy the code, Copy the files and Copy passwords. They are gone from a first migration: the code and files will follow your Transform choices. Passwords are now on the Users step, as a row that says "Will copy passwords: people sign in exactly as before", with a switch to turn it off. A move again or a final sync asks whether to bring the code and files over again, in plain words, because those already exist on the new instance. A migration that had already turned the code or files off keeps that, and still shows it. What the load carries now shows Hold emails and outside connections until cutover under its own heading, saves each change as you make it with no Save button, and says "This site has no settings or keys" instead of "0 of 0".
  • Every Transform step opens with its list, and the wizard only goes forward. The pages and code, the site files, the forms and the redirects were listed only once the plan was built, which reads the new instance and can take minutes, so a person walked past those steps while they said "listed once the plan is built" and had to come back. They come from the old site alone, so they are now listed the moment Analyze finishes and each step opens with them. A step that still waits for its list, such as Users, which needs the new instance, says so, shows how far the work has got, fills in by itself, and holds Next ("Waiting for the people check") until it is ready. Transform no longer says "Nothing to decide", including on a step with optional choices such as Databases: each step says Waiting, Needs you with a count, or Ready, which means its defaults are set and any change is optional. Next says "Next: Forms", and adds "needs you" only when the step it opens does. A migration planned before these lists existed gets them the next time a Transform step is opened.
  • Transform choices save themselves. A choice on a Transform step was kept only once Save and build the plan was pressed, so typing who a form emails, pressing Turn on hCaptcha and then reloading lost both. Every choice is now saved as it is made: a click, a tick or a choice at once, and typing after a short pause. A quiet line by Next says Saving..., then All changes saved, and a reload shows every choice as it was left. Next does not leave a step until its choices are saved; if a save fails, the line says so, keeps trying, and offers Retry. Only the settings that changed are sent, so two tabs changing different things keep both. The plan updates in the background, and nothing asks you to save or build it again. The "Changed, not saved yet" line and its Discard are gone; Undo all still undoes saved changes. A database left behind with a reason is shown as a choice, in grey, not in red; one left behind with no reason yet is amber and counts as a decision, and the "Needs a decision" badge counts the same way.
  • Verify fixes things where they are, and Check again checks only what it says. A code file the result names as missing or different has Copy it again beside it, and copying reads that one file back and settles it on the code check, with no full run of Verify. Each code card has Check these files again, and each file Check this file again, which check only those files. There is one Check everything again, on the Result step, and it says how long the last full check took and asks first. Going ahead with the code check failing records your reason once and keeps the new site's version, without asking again. Links in records and code that still lead nowhere after the files were copied have Point them at the copies, which fixes them and checks the links again. The load also writes again any code whose upload it followed to a new folder: before, those files were left naming the old folder and read as differing on Verify. The page photographs say how many of the site's pages were photographed, for example "50 of 233 pages photographed". A table field with no name no longer stops Transform with a red message. Sending the code to GitHub runs in the background with its steps in the live log, so a large send no longer shows a timeout.
  • Every count says what it counts, and the plan says what will happen. The count beside a list's filter box reads, for example, 11 kinds or Showing 10 of 22 databases, not a bare number, and so does every count on a folded section. Before the load runs, Transform and the plan say what will be copied, and their marks read Will copy and Will skip. While the load runs they read Copying, and afterwards Copied, as the report and Verify do.
  • Read the source moves on at once. After choosing a dry run or a migration, pressing Read the source left the page on the same screen for several seconds while the tool checked both keys and started the migration, so it looked stuck. The page now moves to Analyze the moment the button is pressed and shows Preparing analysis... with its progress bar until the read begins, and the tool answers sooner because it checks both keys at the same time. If the migration cannot start, Analyze says why, with Try again, instead of waiting.
  • The tool tells you when a new version is out. When a new version is deployed while the tool is open, a bar at the top says "A new version of the Migration Tool is out" with a Refresh button and a link to this change log. It checks about every 5 minutes and whenever you come back to the tab, and shows only once the new version of the screens is live. It never refreshes by itself. If you have Transform changes that are not saved, it asks before a refresh drops them. A migration that is running keeps running while you refresh. The cross hides the bar until the next version.
  • Move a migration into an agency. A migration in your Personal account can move into an agency where you are an owner or an operator, with its final syncs, keys, plan, checks, screenshots, reports and history. Press Move to agency at the top of the migration. It then uses the agency's AI limit and the agency's own GitHub connections: if the agency has not connected the GitHub organization the code was going to, an owner connects it in Settings and you choose where the code goes again. The move is written to the Activity of both accounts. It changes which account owns the migration, not where the site goes; to move a site to another instance, use Move again to another instance on the Close step. Agency workspaces.
  • The tool's own emails are in its Email Logs. Every email the Migration Tool sends, such as sign-in links, invitations and the emails about a migration, now goes through the Insites CRM's logged send, so each one has a row in the tool instance's Email Logs, named Migration Tool: and the kind of email. Who it goes to, who sends it, the subject and the body are unchanged. An instance whose CRM is older than 6.1.5 sends them as before, without a row.
  • Each step's own drawing sits before its heading. Every step of a migration now shows its own small drawing inline before the heading, and the second sentence under the heading is gone, so each step starts with what to do. The green tick on a heading such as Connected to the source now sits after the words.
  • SendGrid is built in on v6, so it is no longer a job. Insites sets up email sending (SendGrid) for every new instance automatically, with its own SendGrid subaccount. A source site's SendGrid integration now shows on Transform, Other, as Built in on v6 with a neutral pill, and is not moved, not on the To do list, not counted in what needs you, and recorded in the report as Built in on v6. Every other integration is still set up again in Insites Console.
  • A SendGrid key is never copied. A constant that is a SendGrid key, found by its name or by the shape of its value under any name, shows on the constants list as Never copied: v6 sends email through its own built-in SendGrid account. It cannot be chosen, is not counted in how many constants are chosen, and no load, sync or move to another instance writes it. The report records it.
  • A test account signs in on the old site as soon as you add it. On Plan, Signed-in checks, a test account used to be saved without being tried, and its first sign-in happened after the load, in Verify. Adding one now signs it in on the old site straight away: the button says "Checking sign-in..." until the account appears as a row with "Signed in on the old site" and the page it landed on, and the summary updates at the same time. If it cannot sign in, it says why, such as a wrong password or a sign-in page that is not /login, and nothing is saved until you fix it and add it again. Only accounts that signed in count toward the summary. Saved accounts are listed in a table with Edit (which can change the password, never shown), Check again and Remove, the form clears after each add, and + Add another test account adds one for each kind of person, such as a member and an admin. The sign-in on the new site still runs after the load, in Verify. Sign-in tries are limited to 6 every 10 minutes per migration. When the old site has pages behind a sign-in, Next on Signed-in checks waits until an account has signed in, or until you press Skip signed-in checks, which is recorded. In Verify, an account whose signed-in check failed is listed under Things that need you with Edit credentials and Check this account again, which checks only that account's pages, not the whole verification.
  • A slow site's pages no longer stop the read at the AI pass. Right after the pages were read, the AI pass over collection pages did not watch the clock and did not keep its answers, so every step started it again and the tool's time limit stopped it at the same place until the migration failed. It now keeps the answers it already has, carries on from them on the next step, and asks for more only when there is time left for an answer.
  • Page photographs are faster, and a page that will not photograph no longer holds up the others. The screenshot check now photographs several pages at once, with the old and the new site of each page at the same time, where before it took one picture at a time. Each page has its own time limit. A page that goes past it is closed on its own while the other pages carry on, and the browser is restarted only if it stops answering. When two migrations verify at the same time, the browser service asks the extra pages to wait their turn. A page that fails for a moment is tried again after a short pause. A page that still cannot be photographed shows as could not be photographed with Check again. It is never counted as a page that looks different, and it never fails the migration. Staff are alerted only when the browser service keeps failing, not for each page that needed a second try.
  • Alerts keep their apostrophes. An alert about a run could read "the tool'(a value)'s pages", because the part that hides quoted values took two ordinary apostrophes for quote marks. An apostrophe inside a word is now left alone. Values in quotes are still hidden.
  • A Webflow collection page is built as one page design linked to its database. A blog or any other Webflow collection used to have its item pages copied as static pages until you chose, even when the AI had built a template, because the template did not match every item page word for word. A collection page reads from a database by design, so the AI's template is now used until you choose otherwise, and each item stays a record. The first difference is shown as a note rather than a decision. When the item pages differ in more places than one AI request asks about, the AI is asked about the six that matter most, starting with the page body, and the rest are left out of the template and named in its explanation, where before there was no template at all. Copy each item page as a static page and Leave it for you are still there.
  • A form with nobody to email is a choice, not a warning. On Forms, a form whose Sends each one to is blank now reads, neutrally, that it will save submissions and nobody will be emailed, and it no longer counts as something to fix. Typing an address marks it resolved.
  • The forms checks line up. Each note and button now sits directly under its own line, so it no longer looks as if it belongs to the next one.
  • No dropdown arrow in the database name box. The Copied into box on Forms and Databases showed an arrow when focused. It is gone; the suggestions still appear as you type.
  • A copied Webflow form keeps its plain name. A form's database and form-builder name no longer start with webflow_form_ or webflow_: "Newsletter Subscription Form" becomes newsletter_subscription_form. A name that clashes with another form or a collection's database gets _2. When the new site already has a form's table from an earlier move, named webflow_form_ or webflow_, that table and its form are reused, so moving again or a sync finds them and nothing is copied twice.
  • A choice on the plan updates it in a couple of seconds, not again from the start. Choosing a fix or leaving a database behind used to read the whole new instance again, and ask the old site three questions, as if the migration had just started. A choice changes neither site, so the plan now keeps what it read for 10 minutes and builds from that, with no requests to either site and no AI. On a test migration of 15,000 records, each choice went from about 4 to 5 seconds to about 2. The plan records which choice caused it and whether it read the sites or used what it kept. While it updates, the plan stays on screen and a small "Updating the plan..." note shows only if it takes more than a second; only the load waits for it. The load still reads the new instance again and checks the plan against it before it writes anything, and a new plan still means a whole load again.

October 24, 2026: version 0.8.10

  • The old site's sign-in dates are no longer copied. A move copied each person's last sign-in date from the old site, so the new site's Settings, Administrators list showed a Last Sign In of two or four years ago for people who had never signed in there. Sign-in and activity dates, such as the last and current sign-in, the sign-in count and the last activity, now stay behind, on every profile and for every kind of old site. A person shows no sign-in on the new site until they sign in to it. The people's details check no longer counts a missing or different sign-in date as a difference, and says how many people's old sign-in dates were not copied.
  • A slow site's pages no longer stop the read, and the read says what it is doing. Reading a Webflow site whose pages took longer than one step of the tool started the pages again from the first one on every step, so the tool's time limit stopped it at the same place three times and the migration failed. The pages already read are now kept, and the next step carries on from them. While the source is read, Analyze lists each part of the read, such as the records, the forms, the files and the pages, with a tick when it is done, says which part is in hand and how far it has got ("reading the pages, 41 of 120"), and its bar does not reach 100% until the whole read is done. It says when the tool last moved, says plainly when the old site asks it to slow down and how long it waits, and says what to do if nothing changes for an unusual time. The load and the checks also say when they last moved. If the time limit does stop a part three times, the message now names the part and says to press Carry on from where it failed.
  • Save this choice turns on as soon as the GitHub choice is complete. On Destination, GitHub, typing a new repository's name or the new branch's name left Save this choice held, saying "Choose the organization, the repository and the branches first", until something else redrew the page, so it could stay off for a while with everything filled in. It now turns on the moment the choice is complete, and when it is held it says exactly what is still needed, such as "Name the new repository first". A new repository asks for no base branch: GitHub makes its default branch when the code is first sent. While GitHub checks the choice, the button says so. Once saved, the step says Saved. and what was saved.
  • Next never drops a GitHub choice that is not saved. Pressing Next with a complete choice that is not saved saves it first, then moves on. With an incomplete one, the step says what is missing and that nothing is saved; press Next again to go on without sending the code to GitHub.

October 24, 2026: version 0.8.9

  • Your own account no longer fails the people's details check. The new site records the date you last signed in, and the theme you pick, on your own account there, so from the second check on the people's details check always showed one person who differs: the person running the migration. It now says that line is your own account on the new site and why it differs, and counts it as moved. Any other difference on your account, and any difference on anyone else, still fails the check.
  • Something removed from the new site after the load is named, not just missing. When a table, page, email or other code file the load copied is taken off the new site later, the checks now say the load copied it and it has been removed since, the To do list asks whether the new site stays as it is (keep the new site's version, or leave a table behind on the final sync) or gets it back (Copy all again, or a final sync), and a final sync's plan says it would copy it back. A code file kept as the new site has it, which the new site does not have, now counts as left behind with its reason everywhere. Before, all of these read only "is not on the destination", and the card said the tool could not create them.
  • Page photographs no longer fail with "Infinite loop detected". On larger sites the SCREENS check could fail on most pages, 65 of 66 on one site, with the browser service answering INFINITE_LOOP_DETECTED. The cause was ours: a migration moves forward by starting its own next step, and each request the tool then sent to its browser service carried that chain with it, so from the fourth step on the hosting platform took every request for a loop and refused it. Requests to the browser service no longer carry the chain, so a photograph is asked for the same way on every step. If the browser service still fails on three pages in a row, SCREENS stops asking it and says, in one line, on how many of the site's pages it failed and with which code, so a fault of the tool's own is never read as something wrong with either site. Press Check again to photograph those pages.
  • A nightly sync that stops for you says so, and asks what to keep. When someone changed rows on the new site after they were copied, a night of the nightly sync stops before copying anything, so it does not write over their changes. The Migrations list, the top of the migration and the email now say Nightly sync is waiting for you, and Load lists each changed table with how many rows changed. For each one, choose Keep the new site's rows, which leaves them as they are and stops later nights asking about that table, or Take the old site's rows, then press Carry on to load the night. Before, the night only said "Waiting for you" with "Type the plan code to load", its email said the plan was ready and opened the Transform step, and nothing said which tables had changed or what to do. When a night waits for you
  • The signed-in check finds the old site's own sign-in page. An Insites v4 site signs people in at /admin/login and has no /login, so the check stopped at a 404 and compared no signed-in page. It now tries the address you gave, then the pages the old site says sign people in, then where the site itself sends someone who is not signed in, following the site's own redirects, and the plan suggests that page when you add a test account. A new site that signs people in through Insites Console is reported as not checked, where before it read as a failure.
  • Images a website's stylesheet names by a relative address are copied, and checked. A Webflow or Squarespace stylesheet that names an image or font by a relative address, such as url(../images/hero.jpg), now has that file copied into Assets and pointed at, the way the browser finds it on the old site. Before, only an address written in full was copied, and a relative one was left naming a folder the copy did not have. The Addresses check now also asks whether every image and font a moved stylesheet names answers on the new instance; before, it only looked for addresses still on the old site, so an image pointed at a copy that was never made passed.
  • Forms that check reCAPTCHA have a To do job that names each one. A version 6 instance has no reCAPTCHA keys until Insites sets them up, so a moved form or page that checks reCAPTCHA shows and logs "can't find configuration for CAPTCHA". The To do list now carries Set up the spam check (reCAPTCHA) on the new site's forms, naming each form by its name and the page it is on, with the steps: the keys from Google's reCAPTCHA admin console, set up by Insites support, or a switch to hCaptcha, which needs no keys. LOGS marks the error In a To do job and opens that job. Before, it was marked Yours to fix, and it pointed at Insites Console's integrations, which a version 6 instance does not have.
  • Form emails moved to v6 are now recorded in Email Logs when they send, as Forms 6.1.2 does.

October 24, 2026: version 0.8.8

  • Hold emails and outside connections until cutover. A new plan option, asked on every migration and off unless you tick it. Ticked, every email, SMS and API call the migration copies, such as form notifications, autoresponders and calls to Zapier or Make, is written to the new instance switched off, so testing a rehearsal on a live instance emails nobody and posts nowhere. The plan names each one it holds, and each file whose code sends something the tool cannot hold. They stay off through every final and nightly sync. Press Turn on emails and connections on Finalize, Cutover, or let marking the domain moved do it, and each gets back exactly what it had, read back and recorded in Activity. Verify shows how many are held as a note. Payment keys are never copied: test with Stripe test keys. See Test on a live instance safely.
  • The site's own migrations are recorded as already run on the new instance. A migration runs once on each instance, and the new instance had never run the old site's, so the first deploy of the site's code after a move ran them all again over the copied data. On one site, the seeds of its coach finder made 21 duplicate locations, 2 categories and 10 location custom fields. After the data is copied, the load now records each migration the old site has run as already run on the new instance, without running any of it. The plan's Worth knowing names each one, and the To do list names any that changes a table or a setting, to check. Untick Record the site's migrations as already run on the plan to leave them to run. See What is copied.
  • Every site file is sent with the type its name needs, and checked for it. An image or script the tool copies now tells the new instance's storage its type from its extension, as the Insites CLI does, so a .png is served as image/png even when it holds JPEG bytes, and a script holding an SVG in its first lines is served as a script. ASSETS now reads the type each copied file is served with, and fails a file served as the wrong kind, naming it: a browser ignores such a file with no error on the page. Copy again sends it with the right type. See ASSETS.
  • Sending the code to GitHub sends the code in the site's own modules. Code kept in a site's own modules, such as modules/website, is now read back from the new site's export of each module. Before, the tool looked for it in the export of app/, which never holds a module, so on one site 472 of 472 code files were reported as not found and only its 155 site files were sent. A send is now every file or none: when any moved file cannot be read back, nothing is sent, and the card says how many of how many and names each one. See Send the code to GitHub.
  • Sending the code to GitHub keeps the repository's line endings. A file that differs from the repository's copy only in its line endings or spaces is no longer sent, and a changed file keeps the repository's line endings, so the pull request shows only real changes. Before, a send could change 56 files of which 31 differed only in their line endings. See Send the code to GitHub.
  • The migrations list has filters, pages and an Environment column. Each migration now says whether the new instance is Production or Staging, read from its address, and Not known when the address is the site's own domain; the top of each migration says it too. Filter the list by environment, old site platform, stage, status and who started it, and search by address or id. The filters combine, are kept in the page's address so you can share a filtered view with your account, and are remembered in your browser for next time. The list shows 25 migrations a page, "Showing 26 to 50 of 132", and no longer stops at the 50 newest. See The migrations list.
  • Move a migration again to another instance, with its decisions. When a site was moved to a staging instance first, press Move again to another instance on its Close step to move it to production. The new migration reads the old site again and carries every decision from the first move: what is left behind, renamed, dropped, hidden or fixed, the code fixes, the forms, the constants and what the load carries. It starts as a dry run, its plan lists anything new on the old site as needing a decision, and it leaves out what belongs to the staging instance, such as its key, domains and test accounts. The two migrations link to each other. See Move a staging migration to production.
  • A page's Open Graph image follows it to the new instance. The image a page shows when it is shared, set on the page's Open Graph tab in the old site's CMS, is now pointed at its copy on the new instance, once that copy opens. Before, the page kept the old instance's address for it, so the image would stop showing once the old instance was deleted. The same goes for any link in a page's, partial's or layout's settings, and Links to the old site now reads those settings too. A file the old site links to that nothing else in the move copies is copied from the old instance into Assets, under ins_assets > old-site. An image on an outside CDN, or on another instance, is left as it is. A final sync keeps the new address.
  • The old site is checked before you plan. Right after the source's key is accepted, What it holds shows pre-flight checks of the old site: whether its pages answer the tool, and through which way; who is refusing when something is; whether the key works for data, code, files and people; whether the file host answers; robots.txt and the sitemap; whether the address is the site's own domain; and its size with a rough time. Each line is Pass, Warning or Must fix, with what to do. A Must fix line does not stop the plan: it is shown on the plan's summary and on the To do list. Check the old site runs them again. See Pre-flight checks of the old site.
  • A Git repository connection is a To do job. When the old Insites instance commits its CMS saves to a Git repository (Sync CMS changes to Git on its Integrations, Git Repository page), the To do list now has a cutover job to connect the repository on the new instance: where to find the address and the key, where to enter them, and when to switch sync on. Insites Console keeps the repository's address and SSH key for each instance and never gives the key back, so the migration cannot copy them. Before, nothing said the connection was left behind. When the switch cannot be read, the job says so and asks you to look.
  • Each enquiry adds a CRM contact. Every form the move rebuilds in the form builder that asks for an email address now adds the person to the CRM when it is sent: the contact with that address is found, or made with their name and phone number, and the enquiry is linked to it. It is on by default, and the Forms step of Transform lists it for each form under Adds a CRM contact, so you can untick it. Editing the form in the form builder keeps it. Each enquiry adds a CRM contact.
  • Add past enquiries to the CRM. For a website moved before this version, an owner can press Preview on the Close step of Finalize, closed migrations included. The tool lists each form and its enquiries, then links each enquiry with an email address to its CRM contact, making the contact where there is none, and says how many contacts it added, how many enquiries it linked to an existing contact, and how many it skipped for no email address. Running it again adds nothing twice. Add past enquiries to the CRM.
  • The autoresponder always has a Reply-To. Replies to a rebuilt form's autoresponder go to the first address its workflow email goes to, or, until you name one, to the address the old site links to. When the old site names none, the Forms step asks. Where replies go.
  • The old reCAPTCHA script goes once every form uses hCaptcha. The old site's reCAPTCHA script is taken out of the copied pages once no form on the site uses reCAPTCHA, so pages no longer load a script nothing calls. The copied pages now connect early to the new site's file host, where the old site connected to its platform's. The old reCAPTCHA script.
  • Webflow collection lists read their tables far more often. The tool now tells which item each entry of a list shows by the item's name, or a value only that item has, printed as the whole text of one element, before it looks for a value inside a longer text. Before, a short value such as a service named "Drain unblocking" also sat inside other items' longer service lists, so those entries looked like two items and the list was left showing what it showed on the day it was read. Two entries that come to the same item are never accepted.
  • One list that cannot be rebuilt no longer fixes the others. A list the tool cannot work out stays as the live site showed it, and is named in the plan with why. The other lists on the same page still read their tables. Before, one such list left every list on its page fixed.
  • A collection whose item pages answer 404 has no item pages. When Webflow publishes a collection's template page but every item page the tool reads answers 404, the collection is treated as having no item pages. Its lists show every item that is not a draft and not archived, and an item added in the admin shows without a Published address, as for testimonials and logos since 0.8.6. A 429 or a 500 is not an answer, so it never counts.
  • The tool introduces itself the same way everywhere. Every request the tool makes to a site now sends the User-Agent insites-migration-tool/ and the version, and the header X-Insites-Migration-Tool: 1, so a host can allow the tool. Before, it sent seven different User-Agents. When the old Insites hosting itself turns the tool away, SITE and CONTENT now say it is on the Insites side and that you can carry on, rather than to ask the site's owner. See how the tool introduces itself.
  • Pages bot protection turns away are read through the tool's browser. When the old site answers a plain request for a page with 403, SITE, CONTENT and the old-page reads behind LOGS read it again through the browser that takes the SCREENS pictures, and say how many pages they read that way. At most 40 pages in one verification, one at a time, and never the old site's data. A page the browser could not read either stays Not checked, and says to ask the site's owner, or that it is on the Insites side when the old Insites hosting turned it away. See an old site that refuses the tool.
  • Webflow item pages run their animations. A collection's item page now carries its own template's Webflow page id, its collection and its slug, as Webflow gives it. Before, when the site had a page at the collection's address, such as Our Work, every item page carried that list page's id instead, so Webflow's interactions never ran on it and anything that fades in, such as the hero on each Our Work page, stayed hidden. The list page no longer claims to be an item. A site moved before this version gets the fix when it is moved again.
  • A collection whose item pages nobody can reach has no item pages. When a collection's item pages answer but Webflow's sitemap lists none of them and no page on the site links to any, as for a site's client testimonials, the collection is treated as having no item pages. Its lists show every item that is not a draft and not archived, so a testimonial added in the admin shows without a Published address. Its item pages still answer at their Published address. A collection whose item pages a page links to, such as a news index, keeps the Published address rule.
  • The empty-looking webflow folder in Assets is explained. The plan and the Webflow guide now say that the top-level webflow folder holds the site's stylesheets, scripts and fonts, which the Assets screen does not list, so it looks empty. The images are in ins_assets > webflow. Do not delete or rename the top-level folder.
  • A guide to how forms move. New pages explain what the tool builds for each form, what happens when a visitor sends one, what Verify checks, the To do jobs, and what happens to a form you change after the move, with diagrams: How forms move, Test a moved form safely and What the tool does not do with forms.
  • A Squarespace checkbox field keeps every choice ticked. A checkbox field with several choices now saves every choice a visitor ticks, as a list, and the workflow email lists them. Before, only the last one ticked was saved.
  • A Webflow file upload field is named, not left half working. Webflow uploads files to its own storage, which the new site cannot use, so a visitor could attach a file and only its name was saved. The field is now left off the rebuilt form, named in the run's log, and the To do list has Add back the file upload fields.
  • A Webflow form with an Action of its own still sends there. A form whose Webflow settings send it to another service, such as a Mailchimp list or a Zapier webhook, is kept as it is on its page, and the To do list asks you to check it. Before, it was rebuilt as an Insites form, and the service stopped getting anything.
  • A Siteglide form Siteglide checked for spam uses hCaptcha. Its layout's reCAPTCHA becomes the platform's hCaptcha, and the form turns hCaptcha on only when every layout it shows draws the check, because a form whose spam protection is on without the check on the page refuses every submission. A form with no check is named on the To do list under Decide on spam protection. Before, every moved Siteglide form checked nothing, while the To do list said it used hCaptcha.
  • Report a problem from any migration screen. Report a problem is at the top of every migration screen and in every error message. Say what happened and, if you like, add a screenshot. The report goes to Insites with the migration, the step, the error on the screen, your browser, the tool's version and the last 50 lines of the migration's log, cleaned so no key and no value from your site goes with it. The page says Sent. We'll look at it and reply in Slack. Each report is on Activity. See Report a problem.
  • A rebuilt form says what it will not do, before you confirm it. When you rebuild a form from another service as an Insites form, the tool now reads the form's own page for what a form of its fields cannot do: rules that show or hide questions, several pages, hidden or prefilled fields, and calculated fields. JotForm forms are read for all four, Google Forms for pages and prefilled answers, and AI can add one the page does not show. The proposal lists each one, with what the rebuilt form does instead, and says to check what the service sends each submission on to, such as Mailchimp or Zapier, which no form's page shows. You can keep the service's form from there. If you build it anyway, the To do list has a job that names the form and each thing dropped, with how to do it again on Insites where it can. A question a JotForm rule shows is now part of the proposal, where before it was left out.
  • A Siteglide form keeps its access rule. A form only some people could send, such as a members-only form, now keeps its rule when the rule is the site's own: it is copied as a policy file and the moved form names it. Before, every moved form could be sent by anyone. A rule that is part of Siteglide's own code, or calls it, cannot run on Insites, so the plan names it and the To do list has Add the access rules back, with the rule's code and the steps in CMS, Auth Policies and the form's Security tab. Siteglide's own submission guard is left behind on purpose, because it refuses anything a visitor's browser sends.
  • Errors from before a copy no longer count after Check again. On Verify, an error the new site logged before the tool last copied its page's code, with Copy this one again, Copy all again or the load, is marked Fixed since when Check again opens that page and it shows no error. It is listed with when it was logged and which copy came after, and not counted. An error logged after the copy, or on a page the check did not open or that still fails, still counts.
  • Turn on hCaptcha works on a Siteglide form. A Siteglide form's code only draws its layout, so the one-click fix in the forms review now puts the check in each layout the form is shown with, where the form ends, and turns the form's spam protection on only once every layout draws it. When a layout cannot take it, nothing changes and the review names the layout. The review also reads the layouts, so a form whose layout already shows hCaptcha is no longer flagged. Before, the fix could not apply, and its advice left out the check on the page, without which the form refuses every submission.
  • Partials in a layouts folder are copied. Insites v6 refuses a partial kept under views/layouts, such as a blog's header in modules/website/public/views/layouts/blog/, so Copy all again could never copy one. The migration now moves each one to views/partials/layouts/, where it keeps its name, so the pages that show it work as before. Copy this one again and Copy all again use the same place, on a migration planned before this version too. A partial whose name changes has every call to it changed, and one the migration cannot move safely is on the To do list with what to do. Partials in a layouts folder.

October 23, 2026: version 0.8.7

  • Links to the old site follow their files. When your code or records link to an uploaded file or a site file on the old instance by its full address, the load now points the link at the copy on the new instance, after checking that the copy opens. Before, replacing the old file address with the new one changed only the start of the address. The new instance keeps uploaded files in new folders, so those links did not open. A new check, Links to the old site, lists every link that still names the old instance or does not open, with every place it is, and the To do list gets a job for them.
  • Check again is beside every message that names it. On Verify, a message that says to press Check again, such as "Set it up there yourself, then press Check again" for something the tool cannot create on the new instance, now has the button right there, and so do the To do jobs and the short messages at the foot of the screen that say it. A finished migration cannot be checked again, so its messages no longer say to press it.
  • Pages v6 refuses while searchable are copied not searchable. A page that uses content_for or include_form, itself or in a partial it shows, is refused by v6 while its site search setting is on. The move now copies each such page with searchable: false, and lists each one on the plan's Changes under Pages made not searchable for v6. Visitors see the page as before. You can still fix one yourself on the plan.
  • Check the pages that differ again from Before cutover. The To do job Review the pages that differ now ends with Check again, with the button beside it, so you can see which pages still differ once you have fixed them.
  • Errors that also happen on the old site are said apart. On Verify, for each page the new site logged an error on, the tool asks the old site for the same page once, read only. When that page fails on the old site too, the error is marked Also fails on the old site, listed last, and not counted as a migration problem. When nothing in the site's code links to the page, or shows the partial, it says the page may be code the site no longer uses. When the old site could not be read, the error says Not checked on the old site, with why.
  • The site's own user profile types move, with every profile. A user profile type made in the old instance's Permissions screen, such as a member's answers, is now copied to the new instance under modules/ins_profiles/, where Insites v6 keeps them, with every person's profiles of it. Before, the plan could only leave those profiles behind. The plan says which types the migration creates. People's details, on Verify, now counts each kind of profile on both sides, under its old name too, such as modules/ins_permissions/user_information.
  • Old module names in the copied code are changed. The code is now changed to v6's names wherever it names a user profile type of the site's own, such as modules/ins_permissions/user_information, which becomes modules/ins_profiles/user_information, and a form's settings are changed as well as its text, so a password reset form names modules/insites_crm/token. A name the migration cannot change safely, such as one under an old folder that is not a profile type, is left as it is and listed on the To do list with its file and line.
  • Short names in the copied code are made full. Insites v6 finds a query, a form or a database only by its full name, such as modules/website/recover_password, while the old site's code may call it recover_password. The migration now changes each short name to the full one where only one is meant: the one in the same module, or the only one the site has. When it is not clear which one is meant, or the site has none of that name, the name is left as it is and listed on the To do list with its file and line, and the full names that end in it.
  • A date split into day, month and year is one date field. When Rebuild a form reads a form without AI, a question asked as separate Day, Month and Year boxes now becomes one date field named by the question, required if any part was. Before, each part became a field of its own that you had to fix before confirming.
  • A checkbox question with several choices keeps them. When the AI reads a question such as "Which days are you available to work?" as a single checkbox with seven choices, Rebuild a form now proposes checkboxes with all seven, instead of one tick box with the days lost.
  • The forms review says "emailed" only when the form emails someone. The spam protection line on Forms now says submissions are saved, or saved and emailed, to match whether the form sends an email. Before, a form that emails nobody could be flagged both as emailing nobody and as emailing what a bot sends.

October 22, 2026: version 0.8.6

  • Ticking a domain or DNS job checks it. When you tick a job that adds a domain to the new instance or points its DNS there, the tool opens the domain as a visitor would and checks it answers from the new instance. If it still answers from the old site, the job stays ticked and says Ticked, not yet true, with what the domain answered from, and Activity records it that way. Press Check again once the DNS has spread.
  • Go ahead anyway asks when the reason contradicts the To do list. A reason that says something was skipped, while a job about it is ticked as done, gets an Are you sure? that names those jobs. Untick them, or go ahead, and the report keeps both.
  • Close says plainly what it ends. When the 14-day watch or the nightly sync is still on, the Close dialog says first that closing ends it, when the watch started and when it was due to end, and which checks still fail. You tick a box to say you understand before it closes, and the record of the close says what it ended.
  • The same decision is recorded once. A tick, a reopen, a nightly choice or a cutover step that is already what was asked changes nothing and adds nothing to the record, however it arrives twice. The page also sends a write only once while it is on its way.
  • Nightly syncs sit under their migration. On the Migrations list each night is a Nightly sync under its migration, started by the nightly sync, and a busy week of nights no longer pushes the migration off the list. On Activity a night's lines name the migration, with the night's sync beneath it, and what the nightly sync did is the tool's, not the person who switched it on.
  • A paused nightly sync says so. When a night is skipped because a key no longer works, the run and the Migrations list say Nightly sync paused: the new site's key no longer works, with a way to give a new key. A new key, or the next night that runs, clears it.
  • A big load carries on from where it stopped. A load runs in parts of about ten minutes each. Each part now starts after the databases the parts before it finished, instead of reading every database again from the start. A new plan, another approval, or Carry on after a failure checks every database again. Each nightly sync still compares every database and loads only the records that changed.
  • The load's counts are the whole load. People, people with their profiles, passwords copied and files copied now add up across every part of the load. Before, they showed only the last part, so a load of 17,302 people could say 0 had their profiles written. People the load itself created are no longer counted again as already there.
  • Every option on the plan says what it keeps and what it loses. Under each option, such as Create it from the data, Leave these user profiles behind or Apply this fix, the plan now says what is kept, what is lost, and gives a short example. Create it from the data also says that it makes a normal database the site can use, not a holding area for content that cannot move. The same words are in Every option, in plain words.
  • The plan asks when your reason argues against your choice. When you choose to leave something out and your reason says it is needed, for example leaving a profile behind because it is required for login, Apply asks Are you sure? and shows what will be lost. Change your choice, or confirm it. A reason such as not required or no longer needed is not asked about. When your reason argues against your choice.
  • Ask knows the tool. Ask about this migration now also reads these docs, the screens and their buttons, who fixes each kind of problem, who is asking, and where the migration is at the moment you ask. So it can answer how to change the plan, who fixes an error, or where to get the moved code, and it links to the docs page it read. It answers you by name and never tells you to ask yourself. A plan warning about a very large move now says to contact Insites support. Ask about a migration.
  • Delete a migration you no longer need. An owner, or you in your Personal account, can delete a migration, such as a try that failed or was stopped, after stopping it if it is working. It leaves the Migrations list with all its runs, its saved keys and copies of the old site are destroyed, and a watch or nightly sync stops. Nothing on the new site is removed, and it can no longer be rolled back. Activity says who deleted it. Delete a migration.
  • Copy all again works like Copy this one again. Both buttons now copy a file the same way, so a code file whose name starts with an underscore is fixed by either. Pressing Copy all again again tries every file that still differs, including files an earlier press could not fix, without waiting for Check again. When a copy does not match, the card says why: the new site refused it (with its answer), it is still not on the new site, or it was written but could not be read back to compare. It no longer says "0 fields still differ".
  • The Adobe Fonts job on a Webflow site is raised only when it is needed. The To do list used to ask you to add the new domain to the site's Adobe Fonts kit whenever a page loaded one. Adobe Fonts web projects serve any site that has their embed code, so that job was usually wrong. The check now asks Adobe Fonts for each kit, and one of its fonts, as the old site and as the new instance. The job is raised only when the kit serves the old site and refuses the new address, which an older kit with a list of domains can do, and its steps say where that list is. When Adobe Fonts could not be reached, the job says the fonts were not checked and asks you to look at a page, rather than asking for a domain.
  • A check that could not read the site says Not checked. When a check could not read most of what it compares, such as a night the old site gave no answer, it reads Not checked rather than failed, with what could not be read and why, and a Check again button. It does not count against the migration and is never offered Copy again. A check that found anything different still fails. Earlier verifications read the same way. Custom user profile types no longer fail Everything the source holds: they are counted as for you to set up, and the To do list has the job to recreate them.
  • Keep the new site's version of a code file. When your team changed a code file on the new site on purpose, such as a fix from QA, press Keep the new site's version on the file, or keep all of them at once, with a reason if you like. The card turns green with who kept it and when, and the decision is in Activity and the report. CODE no longer counts the file as a problem once you check again, and Copy all again, a final sync and a nightly sync never write over it. Copy the old site's version again undoes it. Keep the new site's version.
  • Code no longer differs on what the new site sets itself. Insites v6 runs every form's background job at the default priority, whatever is written, so a form's background priority is no longer compared. Copy again could never change it, and it was the only difference on many portal and gallery forms. A value that differs is always shown exactly, so empty text, nothing and a number never read the same. When every code file still listed was copied again and still differs, the problem says copying again will not help and offers to keep the new site's version first.
  • Suggest a fix. On Verify, Things that need you, each problem has a Suggest a fix button. AI reads what that check found, including why Copy again failed, and says what is wrong, why, and the exact change. When one of the tool’s own buttons fixes it, such as Copy this one again or Accept the person as they are, it offers that one button, and nothing changes until you press it. A page whose address Insites v6 refuses is told so, with the change to its address, rather than copied again. Suggest a fix.
  • Rebuild a form from another service as an Insites form. On Transform, Forms, a JotForm, Typeform or Google Forms form embedded in a Webflow page has Rebuild it as an Insites form. The tool reads the form's own page and AI proposes the Insites form: its fields with their kinds, required fields and choices, and its thank-you message. You check it, say who the workflow email goes to, and confirm. The plan then builds it in the form builder with hCaptcha and its emails on the new instance's sender, and puts it in place of the embed on every page that carried it. File uploads are listed as left out, for you to add in the form builder. Nothing changes until you confirm. Rebuild it as an Insites form.
  • Check the forms before the load. Transform, Forms reviews each form the move rebuilds and flags a form that would post to nothing, a field with no label, a form that emails nobody, a form with no thank-you message, a field that looks like it collects sensitive information, and a form with no spam protection. Where the tool can fix it, one button does. AI on the Forms step.
  • Webflow: a collection item's Published address is easy to find, and every link uses it. In the admin, Published address now sits right under Slug, and its help says to fill it in to show the item on the site. Links to an item, lists and the item's own page all read the Published address, so a link always leads to the item's page, even after Slug is edited. An item added in the admin is on the site once its Published address is filled in. When you duplicate an item, give the copy its own Published address.
  • Webflow: lists of a collection with no item pages show every item. A collection with no pages of its own, such as testimonials or logos, has no address to fill in, so its lists now show every item that is not a draft and not archived, including items added in the admin. For these collections, Draft in Webflow and Archived in Webflow hide an item while either is on, and the admin says so. Collections with item pages still list only items with a Published address.
  • Webflow: the group of Webflow's own fields says it is for reference. In the admin, the group that holds each item's Webflow id, Draft, Archived and last published date is now called From Webflow (reference only).
  • Webflow: multi-image fields have an image uploader. A multi-image field now moves as the Data module's own multi-image field. In the admin it shows an image uploader with the item's images, in Webflow's order, where you add, remove and download images. Before, it showed one text box per image address. Each image is copied from Webflow into its own attachment, and the collection page shows the images from there.
  • Webflow: the site's images and documents are in Assets. Images, documents such as PDFs, video and sound are now copied to the webflow folder of Assets in the new instance's admin, under ins_assets, where editors can find, replace and download them. Before, they went to a folder the Assets screen does not list. Stylesheets, scripts and fonts stay where they were. Pages and stylesheets name the new copies.
  • Check again no longer adds the same job twice. An error that reads a little differently on a later check, such as when the new site lists one more name in its "did you mean" suggestions, stays the same job, with its tick and its Teamwork task, so pushing to Teamwork again does not make a second task for it. A job whose cause the latest check no longer finds is not deleted: it moves under No longer needed below its list, with who ticked it, and is not counted or pushed. It comes back as a job if a later check finds the cause again.
  • Webflow: move an earlier site's files into Assets. For a Webflow site moved before this version, an owner can press Preview the move on the Close step of Finalize, closed migrations included. The tool lists what changes, then copies the site's images, documents and videos into Assets, points every page, layout, stylesheet and record at the copies, and opens every page to check each image. The old copies are removed only after a check that passes, when you confirm. A closed migration asks for a key for the new site, used for this move only. Move a Webflow site's files into Assets.

October 22, 2026: version 0.8.5

  • A page for coming back from GitHub. After you install the Insites GitHub App, or change its repositories, GitHub brings you to a page that says it is installed or updated and names the organization. An owner of the account you are working in connects it with one button. Installed the App on GitHub first?
  • Only a GitHub organization owner can install the App. The GitHub step says so, and links to the App's settings on GitHub, where an owner adds a missing repository. If you asked the owners on GitHub instead, the tool says your request was sent to them. If your repository is in an organization not connected here yet, the step says to connect that organization, and a personal account is labeled as one. Installing needs a GitHub organization owner.

October 21, 2026: version 0.8.4

  • The tool checks which Insites an instance is. When you connect, it reads which Insites an instance is from the modules it holds. An Insites v4 instance chosen as Insites v5 is told so and stopped before anything is read, because the Insites v5 source cannot move v4's CRM, people's profiles and activities. A migration started from a v4 instance as Insites v5 before this version stops the same way when it next reads the instance.
  • Every moved email sends from the new instance's sender. Each email's From now follows the sender set for the new instance in Insites Console, now and if it changes later. An email that sent from an address of the client's own keeps that address whenever Console lists it for the new instance, and the Console default otherwise; replies go to that address when the email had no Reply-To. An email whose sender was worked out from the form, such as the visitor's address, sends from the new instance's sender, with replies going to that address. An email that chooses between senders in code is moved as it was and is on the To do list. If the new instance's CRM module is older than 6.1.2, which these emails need, the plan is blocked until the CRM is updated in Insites Console. The plan's changes list every email, form emails included, with its old sender and its new one.
  • Plain words on every screen. Every screen, email, report and the To do list was reread for someone new to the tool. Lists lead with what a thing is, such as page /about or Contacts (CRM), and the file path or table name sits under Technical detail. Rows are now records, tables are databases, and properties are fields. Assets is now Site files, and its folders say what they hold. The checks Rows, Tables and columns, and References between rows are now Records, Databases and fields, and Links between records. Crawlable now reads Search engines can find it.
  • What it holds counts what you would count. Each Insites module card leads with contacts, companies, activities and tasks for the CRM, opportunities and pipelines for Pipelines, and each database by name with its records. Table names and counts sit under Technical detail. The Result has a new In your words table that shows each count beside the same count on the new site.
  • The migrations list shows who and how far. Each migration shows who started it, its stage and step, and a small progress bar that moves during the load.
  • Push to Teamwork under any task. Once you choose a task list, Under task lists every open task in it at any depth. Search by a task's own name or by a name above it. Each job is pushed as a subtask of the task you choose, or at the top of the list as before.
  • Done in one place is done in the other. Marking a pushed job done, or reopening it, does the same to its Teamwork task. Closing or reopening the task in Teamwork does the same in the tool. Jobs pushed before this version are left as they were until you push them again.
  • Send the moved code to GitHub. On Destination you can choose a GitHub organization, a repository or a new one, a base branch and a branch name. After the load, and again after a final sync, the tool sends the moved code to that branch with a pull request into the base branch. It never writes to the base branch.
  • Stay signed in. A sign-in now lasts while you keep using the tool on that device, so you no longer sign in by emailed link every day. A device left unused for more than a week asks you to sign in again. Sign out of all devices, in the profile menu, signs you out everywhere.
  • A goal on every step, and a picture of the old site. Every step says what it is for. Source shows the old site's home page as a signed-out visitor sees it. The small timeline under each step is gone, and the full timeline stays on the first page of Plan, Load and Verify.
  • Siteglide: the API key or your password. Choose one way to connect, and only that field shows.
  • No module is reported missing. Every Insites instance has every module, so What it holds no longer lists modules, and the plan no longer blocks on a module that is not installed. A module the new instance runs at an older version still warns, and the retired Insites core module still blocks on a v6 instance.
  • Code files whose names start with an underscore copy and compare correctly. A shared section such as _hero.liquid that the new instance does not take is now written as a file, the way insites-cli writes it. Code no longer reports it as different only because of the underscore, and Copy again works for it.
  • Password reset links never move. They are hidden when the old site is read and always left behind, on Insites v4 as on v5, whatever a migration's settings say.
  • Webflow: forms from another service are named. A JotForm, HubSpot, Typeform or similar form is kept as it is and named on the plan, in the report's Left behind table and on the To do list. The job says its entries still go to that service, and how to keep them in Insites instead. A collection that describes forms is labeled (Webflow collection, no submissions).
  • Clearer connect screens. The help says which address to use: the live Insites v5 instance, not a UAT or staging copy, and the new instance's own address from Insites Console, not the site's public domain. Password managers no longer fill key fields. Filling in both the key and the Insites v5 Console sign-in says which to clear. An error about the Console access token names that field.
  • Clearer decisions on the plan. Approve says to apply your choices first when they are made but not applied. Why you chose this is marked required. A decision with only one option is a box to tick.
  • The watch email says how to stop it. Each watch email says to open the Watch step and press Stop watching, with a link. In every email from the tool, each address is its own link with a space before it, and From and To are links.
  • Dates match however the old site writes them. A date written without milliseconds, or with a time zone offset, is compared as the same moment, so records and people are no longer reported as different on their dates.
  • The files step waits out a storage outage. When the new site's file storage stops taking uploads for a while, the step waits, then carries on from where it was, instead of recording those files as failed.
  • The AI limit says what to do. When a migration reaches its AI limit, the migration says so, and says to contact the Insites support team with the migration ID and your account to raise the limit for your account. Once it is raised, the same migration uses the AI again. The migration reached its AI limit.
  • Each step records the right release. A migration's history now names the release each step ran on. Steps run on version 0.8.3 recorded it as 0.1.0.
  • Insites v4 is a source. Choose Insites v4 on Source to move an Insites v4 instance to Insites v6, CRM included. Each contact's profiles join into one v6 contact, administrators keep their status, activities land on the contact they were about, the CRM's dropdown values match v6's own, and the site manager's Global Content becomes the CMS Global Content. Live keys v4 keeps in its tables never move, and the plan names any page of yours that calls a v4 module v6 does not have. Insites v4.

October 21, 2026: version 0.8.3

  • A long load carries on where it left off. A step no longer reads again what an earlier step of the same load finished, such as people's profiles and rows' own external IDs. External IDs are now read and put back 100 rows at a time, and each finished part is kept, so a step that runs out of time loses nothing. The line about who owns rows is said once in a load.
  • Each step records the release it ran on. The migration's history says which releases a load ran on, for example when a load spans an update of the tool.
  • A paused migration starts its next step sooner. When the request for the next step is refused or gets no answer, the tool tries twice more, and a check every minute starts any paused migration that is waiting.
  • A failure is emailed once per cause. If a migration fails again for the same reason without getting any further, the failure is recorded on the migration and in Activity, but not emailed again. A new cause, or the same cause after progress, is emailed as before.
  • The files step waits out a new site that stops answering. It waits for up to 20 minutes, checking now and then, and carries on from where it was once the new site answers. It also makes fewer calls to the new site at once. Activity says how long it waited.
  • An old site that refuses the tool is not compared. When the old site answers every page, its home page included, with 403, SITE and CONTENT list those pages as not compared, and say to let the Insites Migration Tool through the site's firewall or bot protection, then press Check again.
  • Page photographs close cookie banners first. SCREENS closes the common cookie consent dialogs on both sites before taking each photograph, without leaving the page.
  • Rows that took new IDs are checked correctly. Rows compares each row that the load gave a new ID at that new ID, so these rows are no longer reported as not on the destination.
  • Counts say not found apart from do not match. Rows and Code count what they did not find on the new site separately, a row's line names its new ID only when it has one, and CONTENT says where the text first changes. Check again says it runs the checks without loading anything.
  • Siteglide pages. The home page at /home moves to / with a working redirect from /home. A page in Siteglide's blank page template whose content is a whole HTML document now moves with no layout. CONTENT ignores a title that a page's frame repeats inside its body. A page that only redirects is written with no layout when the new site does not have the one it names, and is not a To do job.
  • Webflow redirects with patterns. The tool reads Webflow's redirect syntax: escaped characters, and (.*) wildcards, which become wildcard redirects on the new site. A pattern Insites cannot express is not moved, and the reason is named on the Redirects step.
  • Redirect targets never run as code. A redirect whose new address holds Liquid is not moved, and the reason is named.
  • Addresses with accented letters. A redirect to an address such as /cafĂ© is read the way a browser reads it, so REDIRECTS no longer fails a correct redirect.
  • Sign-ups. Insites staff have a Sign-ups page listing everyone waiting for approval, with an Approve button and the recent approvals. Two approvals at the same moment send one email.

October 20, 2026: version 0.8.2

  • Your Teamwork key, remembered. When you push a To do list to Teamwork, leave Remember this key ticked and the dialog starts with your saved key next time, so you do not enter it again. It is encrypted, kept for you alone in that account, and only ever sent to the Teamwork site you saved it for. Forget it on the dialog or on People; it also goes when you leave the agency, and after 180 days without use. The Teamwork site must now be an address ending in teamwork.com, or a custom Teamwork domain Insites has added. Your saved Teamwork key.
  • Failure messages say what happened, who fixes it and what to do. When a migration stops or stalls, the page, the emails, the PDF and the Migrations list now say what happened in plain words, naming the old or new site. They say who acts, You do this, Insites fixes this or Nothing to do yet, and give one button to the screen that fixes it, such as Replace the key for the new site. The raw error is never shown; a cleaned line for support sits under Details for support. When something goes wrong explains each kind.
  • A long load's progress is seen. People created, rows a later step finds already written, and external IDs put back now count as progress. A large load that keeps moving is no longer counted as pausing without getting further, and is not reported as stalled. A row whose external ID another row already holds is named once in the undo log and not sent again on every step.
  • Applying your decisions is not a stall. Pressing Apply, Carry on or Confirm restarts the stall clock, so a plan rebuilding after you apply decisions no longer sends a "no progress" email.
  • Plan changes from the load's own work are not reported as drift. A table the load itself created on the new site is not called a change on the destination by a later step, and a real change is reported once, not on every step.
  • Page checks read the old site at the address it really serves. When the old home page redirects to the same site's www or bare address, SITE and CONTENT compare pages there, so a site that redirects to www is no longer read as missing pages.
  • The nightly sync checks its keys first. If a key no longer works, that night is skipped and recorded on the migration beside Give the migration a new key, and the person who switched the sync on gets one email. Emails about a nightly run say Nightly sync.
  • Platform module tables on the new site are confirmed by name. A table the load creates in a platform module's private folder, which the instance does not list, is now found by name and its rows load, so a move no longer stops on it.
  • Webflow forms keep each page's look. A form used on several pages keeps each page's own look, labels and thank-you message. reCAPTCHA becomes the platform's hCaptcha. When the new site is on the staging stack, Forms and Verify say that form emails do not reach the people named, and how to test instead. Every step on the launch timeline has a You do this line, and the step you are at has its own button.
  • Every dropdown is searchable. One dropdown is used across the tool, on Activity, People, Transform and the new key dialog as well as the Teamwork pickers. Each has a search box that narrows as you type, works by keyboard and with a screen reader, and keeps its arrow clear of the edge.

October 20, 2026: version 0.8.1

  • The migration page keeps up after a dropped connection. Before, one failed read, such as a wifi drop, a laptop waking or a server error during a load, left the page showing an old status. Now the page tries again after 6, 12, 24 and then 30 seconds, says so while it waits, and clears the message once a read works. A request that gets no answer is given up after 60 seconds, so the buttons never stay held, and an older answer never replaces a newer one.
  • Keyboard focus is easy to see, and there is a skip link. Every button, link and field shows a solid outline when it has keyboard focus, clear in light and dark mode and in high-contrast mode. Skip to main content is the first thing the Tab key reaches on every page.
  • A large migration always saves. The list that matches each old row to its new one is kept in its own encrypted copy, so the migration record stays well under the 4 MB the instance accepts. A migration that fails still saves its failure, so the page can say what went wrong.
  • Long pauses and slow sites no longer stop a step. When the instance asks the tool to wait, the step waits that long and then carries on, without counting it as a failed attempt. Comparing a large table now stops on time and carries on from where it got to in the next step. A write that failed once is retried with the latest state.
  • The watch after cutover looks once at a time. Two looks can no longer overlap, so you get one email per look. Each page has 15 seconds and the whole look 3 minutes. A page that does not answer is listed as not looked at, and if no look was made the closing email says so.
  • Steadier with Webflow and nightly syncs. A Webflow home page that answers slowly or with a server error is tried again. The nightly sync records each night's run on the migration before it starts.
  • Webflow's placeholder image is listed under Left behind even when only the pages of a collection the tool could not rebuild show it, with the number of pages that name it.

October 20, 2026: version 0.8.0

  • A migration starts with Analyze. Transform opens with a first step whose only job is reading the old site: the progress, what it found, and the activity log, with Next held until the read is done. Every key field has an eye that shows or hides the value, and a green tick shows beside Connected.
  • Names and tooltips for new tables. When the load creates a table and the old site gave it no name, groups or tooltips, Transform, Databases proposes them under Names and tooltips for new tables. You edit any part and tick Use these names and tooltips; only then are they written. Only the gaps are filled, a name the old site gave is never replaced, and the request sends field names and types only, never a row's values.
  • Webflow collection pages: a proposed template. When the tool cannot work out a collection's page template on its own, AI proposes one, and it is used only when every item page reads word for word the same. Otherwise you choose per collection on Pages and code: use the proposal, freeze each item as its own page, or leave it. Each collection page the tool could not rebuild now says why, where you look.
  • Ask and Find out more need the operator role. A viewer cannot use them.
  • A second opinion on screenshots. When it is switched on, Verify shows the before and after photographs of a differing page to AI, which says whether the page is the same, differs, or cannot tell, and what changed. A page passes on its word only when nothing on it changed, and is flagged only when something did.
  • Keys stay for as long as the migration needs them. A key given to a migration no longer expires on a timer. It is destroyed when you close the migration, and Finish is now Close. A key no migration uses still expires after 24 hours.
  • Two new launch checks. Redirects confirms every old page address answers a 301 to its new one. Crawlable confirms the new site's robots.txt lets search engines in and names a sitemap, and that every address the sitemap lists is on the new site and answers. Each failure names its address. On a temporary address, a sitemap line copied from the old site is noted, with a To do job to change it at cutover.
  • Under the launch timeline, a table says what each step does and what it does for you. One row each for Before cutover, Cutover, After cutover and Watch. The timeline shows in full on the first page of each stage and as a short row after that. Push to your project management tool is on After cutover too, and the Teamwork project and task list pickers are searchable.
  • The Migrations list says what is next. Each migration shows its next step, such as Decide 2 things or Approve the plan, and the row opens the page for it. A rolled back, failed or stopped migration opens on a card, Where to go from here, with its ways forward as buttons. Every greyed button says why it is held, a refused key says what to do next beside the field, and a clean Verify result skips the two empty pages.
  • You do this. The status for work the tool leaves to you now reads You do this: the tool does not do it, you do, and each one is added to your To do list on Finalize with what to look at. On What it holds, each card opens to list its tables and the items that are yours.
  • Activity. A new Activity page beside People shows who did what in the workspace, newest first: keys, people, approvals, plans, loads and checks, with filters and a CSV download. It never shows a key, a token or your site's content.
  • People. An owner can change a member's role. An agency's People page shows its workspace ID with a Copy button, and the roles page says what each role can do.
  • Emails. Every email the tool sends comes from the instance's own sender, names the account it is about with its number in brackets, and is copied to the Insites team.
  • Works on a phone, and by keyboard. The launch timeline and the landing page steps fit a phone screen. Keyboard focus is never hidden behind the bottom bar. Progress bars are named, quiet text reads at 4.5 to 1, and each page has one heading.
  • Fixes from the rehearsals. A Siteglide site's sitemap listed the home page once per page; it lists each page once. A Squarespace site's files keep their path on the new instance, so every file is served with its cache header and the instance log stays clean. A Squarespace sign-in route is no longer planned as a page. Webflow's own placeholder image, which nobody can read, is left behind and named. Siteglide's robots.txt keeps the site's own rules. A renamed table takes its definition with it.
  • Groundwork for more platforms. Platform names, the HTTP client, the shop, the naming rule and the connector checklist moved into shared packages, so the next platform is built on them. No new platform ships in this version.

October 18, 2026: version 0.7.1

  • Copied SVG and AVIF images keep their file names. Before, a website's SVG and AVIF files were saved on the new instance with no name and no extension, so they did not load as images. Now each keeps its own file name and is served as an image. ASSETS no longer compares a Webflow file against the size Webflow reports, which is often wrong. It checks that the file is there, and says so.
  • Load and Copy again finish when a page is over 4 MB. The Console proxy will not return a page that large, so one big page stopped a final sync, a step run again, and Copy again. Now the tool reads such a page from the instance's export of its code, and writes a big file as a zipped release when a plain write is refused. If the new instance's own copy of a big page cannot be read either way, it is left as it was, named in the report, and given its own To do job.
  • Verify checks a page over 4 MB. CODE now reads the page whole from the same export and compares it like any other file. Before, it compared only the page's settings and counted it as could not be checked.
  • Checks accept the failures the migration did not cause, and show why. A file that is missing on the old site too had nothing to copy, so FILES accepts it. LOGS accepts an error the old site already had, an error in a module Insites provides, the CAPTCHA error until the To do job that sets up reCAPTCHA is ticked, and a form on a page that is searchable on the old site too. Each check lists what it accepted, with the reason, and passes when everything else matches.
  • Workflow emails list every field. The workflow email for a copied form arrived with no fields. Now it lists every field of the submission, including for forms built on Insites v5.
  • CONSTANTS no longer flags a Console address that every instance shares. Every instance one Console looks after holds the same Console address, so finding it on both instances is not a copied key. CONSTANTS still fails when a key that belongs to one instance, such as the Console sign-in key, holds the old instance's value.
  • Insites hears about each new request and waitlist sign-up. An email goes to the Insites team for each new Request a platform and each new Join the waitlist, with what you entered. After a request, the dialog says our team will be in touch.
  • The sign-in link works on a browser that remembers another account. If the browser kept an account that is not yours, such as one from someone else's earlier sign-in, the tool moves you to Personal and says so. If the list of platforms does not load, the step says so and shows Try again. The account switcher now shows on phones.
  • Every email says who it was sent to. The small print at the foot of each email names the address it went to and the account it is about, such as Personal or an agency.
  • Three new words in the glossary. The glossary now explains Databases, Renames and rewrites, and Finalize.
  • Every table the tool keeps is named, grouped and explained. In the tool's own admin, each of its 11 tables has a clear name, its columns sit in labeled groups, and each column has a tooltip. A tooltip for a coded column lists every value it can hold, and a column the tool manages says not to edit it directly. No table or column is renamed.

October 17, 2026: version 0.7.0

  • A migration starts with where you are coming from. Before you start is gone. The first screen asks Where are you coming from?. Then the website address, on its own screen, then the key for that platform, with only that platform's how-to. Links to Before you start open the first screen.
  • Request a platform, and join a waitlist. The last tile, Request a platform, tells us about a platform that is not listed. A Coming soon tile has Join the waitlist, which adds you to the waitlist for that platform.
  • Destination starts in Insites Console. Log in to Insites Console opens Console in a new tab, to create a new, empty v6 instance. Come back and press Next to connect it.
  • The token on its own is enough. On the Destination step, paste the Console access token (it starts iak_) and the tool works out which instance it opens from the v6 instance URL. Pasting the whole command still works, and so does a GraphQL admin key.
  • Clearer help. The field's help and the guides now say to copy the token, not the whole command.
  • Transform has one step for each kind of thing a site holds. The steps are Pages and code, Assets, Databases, Forms, CRM, Users, Ecommerce, Events, Locator, Other and Redirects, then Advanced. Every step shows for every site. Each one lists what the site has, how many, and what happens to each: Copied, Rebuilt, Recreated in Insites, You do this, or Not copied, with the reason. A kind the site has none of says "This site has none." Forms replaces Form submissions, and Users replaces People. The steps.
  • Choose which files are copied, on the new Assets step. The site's own files, such as styles, scripts, images, fonts and documents, are listed by folder with their size. Tick or untick a whole folder, or one file at a time. A file you untick is not copied, with the reason "Chosen not to copy", which you can change. The plan warns when a copied page still uses a file that is not copied. Files that belong to a row in a database go with their row, so they are not listed.
  • Two steps have new names. Tables is now Databases, and Fields and values is now Renames and rewrites. They do the same as before, and saved links still open them. Renames and rewrites and Rows and secrets are under Advanced, for every site.
  • The tool says copy, not move. Everything the load takes over now says copy: Copy the code, Copy the files, Copied and Not copied. Summary and decisions on the plan says Nothing on the old site is changed or deleted. The tool only reads the old site. The summary for your client is now called Migration summary.
  • Forms are recreated in the Insites form builder. Each form gets its database first, then the form on it, with its workflow and autoresponder emails, so you edit it in Forms like any other form. This covers Webflow, Squarespace and Siteglide forms; forms from Insites v5 already were form builder forms. The page keeps its own form, so it looks the same. On the Forms step, choose who the workflow email goes to. A form with nobody to send to still loads, with no workflow email.
  • A form repeated on many pages is one form. A form with the same name and fields on many pages, such as a newsletter form in every footer, becomes one form with one database. Each submission records the page it was sent from, and the visitor goes back to that page. Past submissions from every page load into the one database, and the Forms step lists the pages the form is on.
  • Webflow forms save every field. Each field is saved under the name Webflow gives it, so it reaches its column. A Webflow form whose place on the page is gone no longer stops the site being read.
  • The forms count adds up. On an Insites v5 site, the Forms step says how many forms are your own and how many come with Insites modules, which the new instance already has.
  • One Apply, one new plan. Your choices on Summary and decisions and on Fixes are applied together, and the plan is rebuilt one time with all of them. The run log names each choice.
  • A rollback removes the databases the load created. Before, each one stayed on the new instance, empty. A database that holds rows sent after the load, such as a visitor's form submission, is kept, and the rollback says so.
  • The result says what was confirmed, and why the rest was not. It reads, for example, "688 of 689 confirmed: 1 could not be checked", and names that item and why, with a link to it in the Verification log. An item that differs is "does not match"; one a check could not read, such as a page too large to read back, is "could not be checked", and is never counted as either matching or different. The box is green only when everything checked matches, and amber when anything is short.
  • Each line says what was checked. "Rows", "People", "Code", "Pages answer the same", and its result in words: "26 of 26 match", "101 of 101 there". The same words are in the email, the technical report and the summary for your client.
  • Verify is a guided journey in four steps. Result shows the count and the table of what was checked, always open. Things that need you takes you through what failed, one thing at a time. Worth a look has the page photographs and the errors the new site logged. The Verification log, which was Every check, holds every verification in full, as Verification 1, Verification 2. Links to Every check still work.
  • Everything you must act on is on the To do list. Each error the new site logged that is yours to fix, each item the checks could not check, and each page that could not be photographed is a job, and the job and the place it was found link to each other. A code file too large to read back has a plain page of its own that says Copy again will not help, and what to do instead. Tick each job off when it is done: who and when goes in the report. Finalize says how many are still open, and never stops you.
  • Plan log and Verification log. The history of every plan is the Plan log, with Plan 1, Plan 2. The history of every verification is the Verification log, with Verification 1, Verification 2, and the history of every load is the Load log. The Plan log and the Verification log are in the glossary.
  • Ask about this migration. From the Plan on, ask AI a question about the migration: how something was copied, what happened to a file, why a check failed. It answers from this migration's record only, links to the steps it read, and says when the record does not say. How to ask.
  • Find out more on each To do job. It explains what to do, why, and what goes wrong if it is skipped, in plain words. It replaces Write a task with AI, which only made each job longer.
  • Push the To do list to Teamwork. On the To do list, Push to your project management tool turns each job not done yet into a Teamwork task in the project and task list you choose, with its steps and a link back. Pushing again adds only what is not there yet. Your Teamwork key is used for the push only and never kept. Monday.com and ClickUp are coming soon. How it works.
  • Finish is now Finalize, and it guides the launch in time order. It opens with a timeline of the whole launch that marks where you are, then a step for each part: Before cutover, Cutover, After cutover, Watch, Report and Close. The row of cards that opened other steps is gone. Plan, Load and Verify show the same timeline in one line, so you know what is coming. Rehearse, then cut over.
  • Each To do job sits in the step it is done in. Jobs the new site needs from its first visitor, such as integrations, reCAPTCHA keys, constants and forms, are under Before cutover. Jobs that move the domain are on the Cutover step. Jobs that need the domain on the new site, such as password emails, webhooks, search engines and deleting the old site, are under After cutover.
  • Choose the nightly sync when the load ends. The last step of Load asks whether to keep the new site in step with the old one every night until cutover. A sync you choose starts as soon as the load is verified, and you can change the choice under Before cutover.
  • The watch runs 14 days after cutover. It was 48 hours. It still looks every 6 hours and emails a summary once a day. The tool keeps the new instance's key until the watch ends, however long ago you gave it, so the watch reads the new site's error log for all 14 days. When the watch ends or you stop it, the key is destroyed if it is past 14 days from when you gave it.
  • Small fix: buttons side by side are the same height.

October 16, 2026: version 0.6.2

  • Page photographs work again. Since version 0.6.0 the screenshot service closed its own browser on every page, so no page was photographed on either site. It now photographs one page after another, and still lets nothing from one page reach the next.
  • A page that could not be photographed says so. It is listed apart from pages that look different, with the reason in plain words and a Check again button. Before, it was counted as a page that looks different.

October 16, 2026: version 0.6.1

  • Verify finishes when one page is very large. A page over 4 MB on the new instance stopped Verify, because the Console proxy will not return it. Now the checks read around it: the page is named, its settings are still compared, and CODE says plainly that its content could not be read back. Constants and rows that are very large are handled the same way.

October 16, 2026: version 0.6.0

  • The run page updates as soon as the run changes. It no longer asks every few seconds, so it shows each step straight away, and menus stay open while it works.
  • Nothing is lost quietly. A row keeps its own external id. Before anything on the new site is changed, the way it was is saved first, so a rollback can always put it back. A row is never written over a different row the new site already has: the plan names those rows first.
  • A check that could not measure says so. If a check could not read what it needed, it says what it could not read and does not pass. Before, some checks passed with nothing to compare.
  • More of your code moves. API calls, text messages and access rules at the top of your code now move. A page keeps its response headers, its cache settings and a 307 redirect, a file keeps its cache setting, and your own maintenance page replaces the one a new site starts with.
  • New checks for the new site. The plan warns about text whose backslashes the new site reads differently and offers the fix, and lists any site setting that differs between the two sites under Next steps.
  • Two people cannot start the same move at once, and two saves of a run never overwrite each other. Each save of a run is kept as its own version.
  • A short outage at Insites no longer stops a move. When Insites asks the tool to wait a moment, it waits and tries again.
  • Big sites: a site with more than 200 pages has a sample of its pages compared in screenshots, spread across the whole site, and the result says how many pages the site has.
  • Sites connected with a password before version 0.5.0 must be connected again. The tool no longer signs in with a kept password, and keys kept the old way are refused. Connect the site again with its key, or give the password once.
  • Small fixes: Show more works while the tool is saving, downloads and screenshots show that they are loading, a screenshot always belongs to the run it was opened from, and links in the tool's emails are written so they cannot be changed by what they contain.

October 16, 2026: version 0.5.1

  • A security fix for the sign-in and approval pages. A specially made link could add its own code to the sign-in, sign-in link and approval pages. Every value those pages take from a link is now written so it cannot leave its field, and a check stops the fault coming back. Nothing else changes.

October 15, 2026: version 0.5.0

  • Anyone can sign up. A new account can run one migration at a time, and Insites lifts that limit after a quick check. Ask for access is gone.
  • Webflow collections arrive as Insites CMS collections. You edit them in CMS > Collections and their items in Data. Each item has a Published address: an item with one is on the site and in the sitemap, and emptying it takes the item off. Drafts and archived items stay off the site, and Draft and Archived are kept for reference. Moving a Webflow site.
  • The sitemap is the site's own /sitemap.xml. It lists every moved page that is in site search and every published collection item, and robots.txt points to it. A Siteglide site gets a robots.txt too. Submit /sitemap.xml in Google Search Console once DNS has moved.
  • Your Insites v5 Console or Siteglide password is used once, when you connect, to get the key it opens. Only the key is kept.
  • You can roll back until you finish, for up to 30 days after the first load, and you get an email the day before that closes. If the new site's key has expired by then, you are asked for a new one.
  • Finish removes everything the migration kept: every key, every test account password and every copy, including those of its syncs.
  • Email buttons sign you in for one hour, and only when you are not already signed in. Each email says not to forward it. Migration emails go only to people still in the account.
  • Everyone on a migration sees the same watch and nightly sync, whether they open the migration or one of its final syncs: whether each is on, until when, who started it and gets its emails, and every look the watch has made. Anyone who can change the migration can stop either one, and a nightly sync can no longer be started once the final sync or the domain move is marked done.
  • A sign-in refused because an account needs two-factor now says so, and says what to use instead.
  • Stronger protection behind the scenes. Keys and kept values are locked more tightly, a hidden value shows none of its characters, a test account's password is only ever sent to its own site, and the tool's pages cannot be shown inside another site.

October 15, 2026: version 0.4.0

  • Plainer words throughout. The result says how many items were checked and match, such as "4,295 of 4,352 checked and matching", on the page, in the report and in the emails. Technical names stay under Technical detail. A Webflow site is called a Webflow site, once.
  • Webflow form submissions move by themselves. The Form submissions step no longer asks a Webflow site for a file.
  • The steps follow your platform. A website no longer sees steps it has nothing to decide on, and its field and row rules sit together under Advanced at the end of Transform. Tables says when there is nothing to decide.
  • The big buttons say what they do. Before you load, the page sums up what the load writes and how long it should take. Each button says whether it changes anything and roughly how long it takes. Finish asks you to type FINISH and lists what is still open. Once a migration's copies are removed, the page says so and no longer offers a rollback.
  • Getting started. Before you start lists what to have ready for your platform. Sign-in offers Ask for access, and Insites is told about each request. The docs start with a guide for each platform, including a new Webflow tutorial.
  • Two reports. A one-page Summary for your client, with Insites branding, and the Technical report.
  • Moved pages stay in site search the way they were on the old site, and no longer log an error on the new site when they are saved.
  • A redirect decided by a page's code is checked by asking both sites, and the page says "Decided by the page's code" instead of showing the code.
  • Easier to use with a keyboard or a screen reader. Every field has a name, progress is announced once, people who can only view see why a button is disabled, and you are asked before leaving unsaved changes. Terms such as dry run and plan code explain themselves when you hover or tab to them.

October 14, 2026: version 0.3.1

  • A final sync copies only what changed. Every row with a file used to read as changed, so a final sync wrote each one back and uploaded every file again. A final sync over an unchanged site now writes nothing and copies no files.
  • Copy the files again copies the files. For a file whose upload failed, it reads the file from the old site, uploads it and says how each one went. A storage error is tried again before it counts as a failure.
  • A failed file cannot be mistaken for one you accepted. Each shows its row, its size and whether it opens on the old site, and says so when another file with the same name was accepted as missing. Go ahead anyway lists files that will be missing on the new site on their own.

October 14, 2026: version 0.3.0

  • You get an email when the load finishes, saying what it wrote and that the checks are running, and a second when the checks finish. A nightly sync that loads with nobody waiting still sends only its result.
  • Each error the new site logged says whose it is: yours to fix, with the step; one the old site has too, read from the old site's own log; or one in an Insites module, which is not yours. CAPTCHA links to its job on the Finish list.
  • Choose which pages, partials and layouts move on the new Pages and code step of Transform, the way you choose tables. Leaving one behind that a moving page still uses names the page.
  • The Finish list no longer asks for a layout called application. It is the instance's default, so those pages already render. A page whose layout really is missing is still listed.
  • Text and JSON pages are compared at their real address, such as /robots.txt. Before, both sites answered 404 to the wrong address and the page counted as the same.
  • People has its own place in the top menu, and the top bar shows whether you are working in your personal account or an agency, and lets you switch.
  • The change log is in the top menu, and every entry has a version.
  • The docs have a search box, the docs menu scrolls on its own, and the docs say reCAPTCHA keys never move, so the CAPTCHA error on a new site is expected until you set them up.
  • Emails use the Insites email design, with the plain Insites logo.

October 14, 2026: version 0.2.0

  • A large site moves. 250,000 rows and 20,000 files plan, load, verify and roll back within the tool's limits, where v0.1.0 warned above 50,000 rows. The plan now warns above 250,000 rows or 165 MB of data, and stops at 347 MB of data; leaving tables behind on Transform brings a plan under it.
  • Work cut off by the time limit carries on. Reading the new instance's records, copying files, rolling back and checking all stop when a step's time is up and pick up where they stopped in the next one. A step stopped three times in the same place fails the run and says where.
  • A request too big or too slow for Insites is sent again in halves, down to one row, instead of failing the run.
  • A rollback puts back everything the load changed, rows with their dates included, and the ROLLBACK check reads back each kind: rows, people and their profiles and created dates, code, files and constants.
  • A load can be rolled back even when it stopped mid-write. The tool records what each write will create before it writes it. A person who was already on the new instance at that address is left in place, and the rollback report names them.
  • One move at a time on an instance. A load or a rollback is refused while another migration loads, checks or rolls back the same new instance, and says so. Insites staff can go ahead beside it, and that is recorded with who and why.
  • Nightly syncs are spread across the first hour of the night, with at most two running at once on one Insites stack.
  • A busy moment on the tool's own storage is waited out, rather than failing the run.
  • A large Squarespace site reads its pages across several steps, four at a time.

October 14, 2026: version 0.1.1

  • Carry on checks the keys first. If a saved key no longer works, the page offers Give the migration a new key for that side, beside Carry on. A stopped or failed migration that can carry on keeps its keys, 14 days at most.
  • A test account's password lasts as long as the keys. If it has expired, the signed-in check says which test account to add again. Nothing the migration has done is lost.
  • A v5 source's Connect form says Insites v5 Console throughout, and that the Console password is kept like any key: encrypted, never shown again, and destroyed when it expires or when you finish.
  • A person the new instance already has takes their created date from the old site, the person who claimed the instance included, so USERS no longer fails on them. If an instance will not change the date, USERS says so on its own line. A rollback puts the date back.
  • A form's emails stay as they were. Attaching a notification to its form keeps its trigger condition and delay, so an autoresponder switched off on the old site stays off.

October 14, 2026: version 0.1.0

  • The new instance connects with a Console access token. Paste the whole command from its CLI tab in Insites Console. A GraphQL admin key still works.
  • A v5 source signs in to the Insites v5 Console. console.insites.io now opens the v6 Console, so a v5 source's Console email and password are your v5 Console sign-in. Every v5 Console sign-in failed before this.
  • Connecting a v5 source shows its two ways in: the GraphQL admin key, or all three Console sign-in fields. It names any field the way you chose still needs.
  • Keys last while a migration is in progress. The tool keeps them a day at a time, 14 days at most, and records each time. The Load step says when each key expires. A plan read one day can now be loaded the next.
  • A key that no longer works says so and offers Give the migration a new key, rather than an internal error, on copy again, check again, the final sync, a rollback and the load. Reading what an instance holds with a refused key says so too.
  • A failed run can carry on from the step that failed. Every page of it says why in plain words, with the raw message under Technical detail.
  • A failed or stuck run emails Insites as well as the person who started it, so someone can help.
  • A gateway error pauses a run instead of failing it. A brief error from the network in front of an instance, such as a 520, is waited out and the run carries on.
  • Every record keeps its owner. The person who owns a row, and a column such as user_id that names a person, point at the same person on v6. The new OWNERS check proves it, and the plan names owners the move does not carry.
  • Private files stay private. They are read through signed addresses and written private, the plan lists the private columns, and FILES checks they still need a signature.
  • A row with two file columns keeps both files. Copying the second no longer put the first back at its old address.
  • Files in a renamed or Siteglide upload column are copied. They were read under their new names, found nothing and were called broken.
  • A table defined in a v5 file of another name is created under its own name. v6 names a table after its file, so it was created under the file's name and the load stopped.
  • A table with no definition can be created from its data. The plan offers Create it from the data before Leave the table behind.
  • A row rule that matches nothing stops the plan and says why, with Remove the rule. A website's row can be named by its id on the old site.
  • A form's callbacks are read as code. A key, a link to the old instance or a filter v6 refuses in one is found and handled like anywhere else.
  • Long lists save. Up to 20,000 form submissions and 5,000 redirects travel in pieces. A few hundred was the most that could be saved before.
  • Saving the transform keeps the people you accepted, so a final sync no longer fails the USERS check on them.
  • What a check finds is kept encrypted. A row's values, a person's dates and given submissions are encrypted in the migration's record, and a code difference never shows a header's value or a key.
  • The plan says what this version cannot move safely: a source over 50,000 rows, or a load whose rollback would delete more than 1,000 people.
  • Code outside the usual folders is named. A file at the app's root, such as an API call under api_calls, does not move yet, and INVENTORY now names it as missing rather than counting it as the platform's own.
  • Every list is read in a fixed order, so nothing is read twice or missed on a large instance.
  • A redirect made in Siteglide's admin moves at the same address, sending to the same place.
  • Rollback and Finish wait for a working run, and name it. A run planned again after a load loads again.
  • What it holds lists every table, empty ones too, marked Created empty, and its counts add up. A module card's You do this count includes a row whose number the instance cannot tell.
  • A run opens on Transform once both instances are read, until someone has changed something.
  • A page on a layout the migration does not copy says what a layout is and what to do about it.
  • A person waiting for a name in the v5 CRM no longer stops the load. Each gets a free slug made from their name.
  • Sign-in limits apply to each network address, and a sign-in link signs in only once, even when opened twice at the same moment.
  • New and updated docs: Create the v6 instance, the keys page with both v5 ways in whole, how long a key is kept, a note that applying the plan writes nothing, and a warning about test accounts on a live site.

October 9, 2026: version 0.0.11

  • An API call's request headers move. The admin API turns a notification's headers into a form the instance then refuses, so a notification that sends headers either did not move or moved with headers that broke every send: the docs site logged 56 failed sends. The tool now writes the headers the way the command line does, as the notification's file, exactly as the old site has them, Liquid included. On a migration already loaded, Copy all again on the code problem writes them.
  • The three result pages are built the same way. The plan, the load and the checks each show what they did, which pass at this site it is, the detail, then every earlier pass.
  • Connecting Squarespace lists the key's permissions in the same table as Webflow, and an Insites instance whose tables are all in modules says so in plain words.
  • A constant the new instance already has is not replaced without you choosing it. The plan compares each constant by fingerprint with the new instance. One the new instance holds with a different value starts unticked under Constants to move, and says so; tick it only to replace that value. One that is already the same says that too. The record of the load names any you chose to replace.
  • The checks read the new site's log. After every other check, the new instance's log is read from the moment the load began, which takes in the load and every page the checks opened. Each kind of error is listed once under Worth a look, with how often, on which pages and in which file: a form whose reCAPTCHA keys are missing, a partial that did not move. It does not decide whether the move verified.
  • Copying a problem again shows how far it has got. The button gives way to a bar, how many are done out of how many, and the time left, updated about every half minute. It turned for up to four minutes at a time with nothing else to go on. Accepting everyone as they are shows the same.
  • A copied file keeps its new address. A row whose text named another copied file was written again with its own file column back at the old address. The address each copied file was stored under is now read back, so a name the new instance writes differently no longer counts as a difference.
  • The list and the run agree on whether a migration is finished. A run whose final sync was finished showed buttons the tool then refused.
  • A Squarespace export with accented headings imports every column. A heading such as "PrĂ©nom" matched no field and its values were left out.
  • One word for each thing. Undo takes back an acceptance or a choice, Next names the next step on every page, Finish the migration and Start a new migration read the same everywhere, and the history tables are each "of this site". A long list says when it shows only part of what it holds.
  • An instance's own keys never move. Insites issues each instance keys for itself: the key Console signs people in with (insites_console_sso_key), the other insites_ keys, and jwt_encryption_secret. They were ticked under Constants to move like any other, and moving the Console key from the old instance meant nobody could sign in to the new one through Console. They are now listed as never moved, cannot be chosen, and are not written even by a sync that carries an older choice. The Constants check fails if the new instance holds the old instance's key.
  • The Fixes step says what it needs from you. It opens with the choices to make, or with Nothing to do on this page. Each finding's mark says what to do: Fix to choose, Stays behind or To do after the load, in place of "Check" on everything.
  • A page on a module's layout is no longer a finding when the new instance has that layout. The plan looks. When it does not, giving the page its layout is a job on the To do list, and so is a policy whose HTTP status the admin API cannot set.
  • Links to the old instance, not "addresses". In Insites an address is a CRM postal address, so the Fixes step lists links and names each kind: the site's custom domain, which needs nothing, the old instance URL, and its file storage URL, each with where it is used.
  • Get the report is on the Finish stage only. It was also on the Plan pages.
  • Every time a site moved, in one table. The Plan, Loaded and Verify steps each list every plan, load and check of the same site onto the same destination, across every run that moved it: the run and what kind it was, the date, the time, who started it and what it did. A final sync's Loaded page said "0 rows written", which was true of that sync and looked as though nothing had ever moved.
  • Loading and verifying are one card. How far along, what it is doing now, the bar and every part sit together, and every part shows its own number: the tables, the people, the rows, the code, the files and the constants, and each check's count once it has run. The status line under the bar, which repeated the footer, is gone.
  • The footer says what the tool is doing. It read "25 of 26 rows written" while the load copied the files. It now names the part in hand, the same as the card, and the rows count to the end when the last table's rows were all already there.
  • What failed is a short list of problems. The Result step says in plain words what needs you, such as "340 of the site's own files are not where the pages look for them", with one button for all of it: copy them all again, accept them all as missing, or accept people as they are. Open a problem to go through it five at a time. A long result was one page of every row and file with a button on each.
  • Old site and new site. What differs is shown under On the old site and On the new site, rather than "Should be" and "Is".
  • Every list works the same way. A list shows five and a button for the rest; a sentence that names a few ends in "and 12 more", which shows the rest. A check lists up to 500 of what failed, was 50, and says when it listed fewer than it found.
  • How different a page looks is measured against what it shows. A page with no stylesheet read "1.7% differs", because most of a docs page is white. The share is now of the page's content: that page reads over 40%, a changed date about 1%. Press Check again on a migration checked before today to measure its pages this way.
  • A module's own files are stored where its pages ask for them. A file at modules/website/public/assets/styles/app.min.css was stored under its full path, while pages ask for modules/website/styles/app.min.css, so a site moved with its stylesheet in a module had every page unstyled. A file now counts as already there only when it answers where the pages ask for it.
  • Pictures of every page open. The home page and any page with a slash in its address could not be shown.

October 8, 2026: version 0.0.10

  • A form's emails are attached for you. Each email, SMS and API call notification a form sends on the source is attached to the same form on the destination, and the Code check fails if a form does not send what it did. Before, each was a job on the to-do list.
  • A form's spam protection moves with it. A reCAPTCHA or hCaptcha setting is written as it is. Only a reCAPTCHA v3 setting with no action, which the destination cannot take, is still a job.
  • The to-do list names what it is about. The people who need to reset a password by name and email, each integration with where its key comes from, and for translations the files and the keys each one uses. A translation is now looked for in the Liquid only: JavaScript that read a||t was counted as a translation.
  • Verifying is a checklist. Each check is ticked when it is done, the one in hand shows its count (the screenshots say "14 of 48"), and the top line says how far along the whole verification is.
  • Every wait looks the same. Opening a migration, reading what an instance holds, loading the sources, the transform settings and the list of migrations each show the moving blue bar and what it is waiting for.
  • Watch emails say what each problem means. The same error is listed once with how many times it was logged, and each problem says who owns it and what to do. An error in code Insites provides is marked as nothing for you to fix, and a site whose pages all answer is no longer reported as having problems.
  • Each watch email says which it is, such as "watch email 2 of 3", when the others come, and what the watch checks. The watch now sends a last email when it ends.
  • The button in an email signs you in. It is a one-time link for you, good for 24 hours, that lands on the migration. Already signed in, it goes straight there. Signing in from a migration's page also brings you back to it.
  • The emails use the new Insites layout: a larger logo lined up with the content, and links to Insites Console, Privacy and Terms in the footer.
  • A page no longer jumps to the top while a migration is running.
  • Decide everything, then build the plan once. Each thing the plan asks now lists its options with what each one does, and you choose and give a reason for every one before anything changes. Apply applies them all and builds the plan again once, with the fixes ticked on the Fixes page. Before, each choice rebuilt the plan on its own. Resolve what the plan asks.
  • Redact says what it removes. It replaces the whole value, and when that value is long, such as a page of documentation, the option says so.
  • The Transform pages say what happens. Redirects lists the source's redirects, or says there are none. Form submissions shows where each form's submissions are kept and how many move. People shows how many people already have an account on the destination and explains both choices. Each page says whether there is anything to decide.
  • Undo all my transform changes replaces Reset to the defaults. It shows only when something has changed, and lists what it removes before it does.
  • Loading is a checklist. Each part of the load is ticked when it is done: the tables, the people, the rows, the code, the files and the constants. The part in hand shows its count and, once it has measured its pace, how long it has left, and the top line says how far along the whole load is.
  • The confirmed load reads as a list: what was approved, every decision made on the plan with its reason, and the plan code.
  • A large set of uploaded files no longer stalls the load. The step that copies them pauses on time and carries on, skips files it has already copied, and counts them, so the page says "120 of 574".
  • A file named with a space can be fixed. The fix for a page such as external_docs copy.liquid was refused.

October 7, 2026: version 0.0.9

  • Nothing you do is overwritten. Every save of a migration is checked against the latest copy, so one made from an older copy, by another tab, another person or the tool itself, is done again on the latest one rather than writing over it. The watch, the nightly sync and the expiry sweep add their part to the latest copy too.
  • A cutover with failing checks asks first. The Cutover step lists the checks that still fail and holds back the final sync and the domain steps until they are fixed or accepted, or until you say why it is fine to go ahead, which goes in the report.
  • Finished is a status. A finished migration, and every run of it, reads Finished at the top of its page and in the list, which can show only finished ones.
  • Accept missing files on the Result step, where the failure is shown, and Accept all remaining at once with one reason.
  • Where the Finish stage stands opens each of its steps: To do, cutover, nightly sync, watch, report and close, each a click away.
  • Accept a person as they are. Someone who already had an account on the new instance, such as whoever set it up, keeps their own created date, which failed the people check with no way past it. Press Accept as they are on the Result step, with a reason, then Check again.
  • Cutover and Keep in step are separate steps. Keep in step says what the nightly sync and the 48-hour watch each check, how often, and how many emails to expect. Once the final sync has run, its button becomes Run the final sync again and is no longer the main button.
  • One place destroys the keys. The To do list no longer has jobs for the watch, the report or destroying the credentials, and the cutover no longer has a Finish step: each is done in its own step, and Finish migration on the Close step is the only place the keys are destroyed. A finished migration is a record, and offers nothing that needs its keys. Finishing also stops a watch or nightly sync that is still on.
  • A clearer new-key dialog. Each field names its instance, only the chosen instance's fields show, and the button says what it is doing: testing the key, using it, then starting the checks.
  • Plain words while it works. Each stage that runs says what the tool is doing in a sentence, and the technical detail is under View the activity log.
  • Stages and steps. The list down the side names the seven stages, and each stage's pages are its steps. The footer says where you are, for example "Stage 4 of 7" and "Step 1 of 5", and its button names where it goes, such as Next: To do.
  • Ticks stay ticked. A job ticked on To do, or a cutover step marked, while the checks were running was lost when they finished. It is kept now, and a final sync starts with the ticks and cutover steps of the migration it follows.
  • Accepting a missing file is instant. Each file is ticked off as soon as you press Accept as missing, and Take back undoes it. The checks no longer run after each one: go down the list, then press Check again once. Accepting the same file twice records it once.
  • A v5 task comment's module moves to its task. The v5 CRM's 2024 task migration wrote "crm" on each comment it copied, in a field neither CRM declares. v6 keeps the module on the comment's task, so the field is left behind with that reason instead of stopping the plan.
  • Connectors are available or beta. An available connector is in the Source stage for everyone. A beta one is being proved on real sites, is offered only where Insites switches it on, and is marked Beta there. Connectors.
  • The tool reads only public addresses. A source or destination address inside a private network, or one that leads to one, is refused with the reason, and every redirect is checked the same way. A page or file too large to copy is reported rather than read.
  • Forms on a module's own tables move. A form that saves to a table an Insites module provides, such as one of the Ecommerce module's, was refused because the platform's list of tables leaves module tables out. The tool now knows each module's tables, and INVENTORY looks for every table rather than assuming the platform's own are there.

October 6, 2026: version 0.0.8

  • The tool lives at migrate.insites.io. Every link in its emails goes there, and the old address sends each page to the same place on the new one, so a link in an earlier email still works. The emails now carry the Insites logo, as other Insites emails do.
  • Squarespace is available to everyone. Choose Squarespace on the Source step. Move a Squarespace site walks through a whole move, shop included.
  • A checklist written for a Squarespace site. The site's domains and DNS, with its email records left alone; the shop's Stripe keys and webhook; what Squarespace's orders paid for shipping and the discount codes they used; receipts from Stripe; the gift cards for you to honor; where each form sent its submissions; the shop's customers, who check out as guests; and keeping the Squarespace site, and the services billed beside it, until the watch ends. After the move.
  • A Squarespace site's sitemap and robots.txt move. The sitemap lists every page that moved, at /sitemap-pages.xml, and robots.txt keeps the site's own rules and points to it.
  • The plan names everything a Squarespace shop leaves for you: payments, shipping and discount codes, order and form emails, customer accounts, and download and service products.

October 5, 2026: version 0.0.7

  • A Squarespace shop sells on Insites, in beta. The shop goes into the Insites Ecommerce module: products, variants and options, categories, orders with their lines and payments, and every profile as a CRM contact. The new site gets a cart and a Stripe checkout through the site's own Stripe keys, and each product page's Add to Cart works. The shop.
  • Squarespace forms send to Insites, in beta. Each form and newsletter block on a moved page is rebuilt to send to the new site, with Squarespace's look, fields and message, its captcha, and a table for what people send. Forms.
  • Squarespace redirects and past submissions. Paste the site's URL Mappings on the Redirects step, and add each form's exported submissions on the new Form submissions step. Redirects, Past form submissions.
  • Squarespace pages, in beta. Every page a Squarespace site's sitemap lists moves to the same address with its design: styles, scripts, fonts and images, and every file Squarespace's scripts fetch as the page runs, found by loading each page in a browser. Nothing on a moved page loads from Squarespace. What moves.
  • A destination emptied many times loads. A load used to stop when the destination held more than 1,000 deleted records. It now reads them all, a page at a time, and stops only when it cannot.
  • A changed file is replaced on a final sync. A stylesheet or script the tool rewrites is sent again on every run. When the destination held it under another name, the new copy was refused and the old one stayed. It is now sent under the name the destination holds.
  • Squarespace, in beta. A Squarespace site's shop moves through an API key made in the site's settings: products and variants, every customer profile, the people with an account, orders and transactions as a record, and product images. What you need.
  • Siteglide is available to everyone. Choose Siteglide on the Source step. Move a Siteglide site walks through a whole move.
  • Siteglide forms move. Each form a moved page shows becomes an Insites form writing to the form's moved table, with the same layout, hCaptcha and page to go to after sending, so a page with a form now moves too. The form's emails move with their wording and recipients, and the checklist asks for them to be switched on: Siteglide sent them from its own code. What moves.
  • A checklist written for a Siteglide site. Domains from the Siteglide Portal, new passwords for everyone with an account, the form emails and their recipients, the site's analytics counting visits to the new instance, pages that stayed on Siteglide, and keeping the Siteglide site until the watch ends. After the move.

October 4, 2026: version 0.0.6

  • Siteglide pages move. Each page moves at its address with the partials and page templates it uses, translated to run on Insites: Siteglide's head and foot, headers, footers, content sections, code snippets and menus become Insites code, and menus read the moved menu table. A page that calls Siteglide code the tool does not translate yet, such as a form or a module list, stays on Siteglide and the plan names it. How pages are translated.
  • Siteglide, in beta. A Siteglide site's data moves through Siteglide's own service, with the site's API key or your Siteglide password. Each module, web app and form becomes a Data table named the way the site names it (FAQ, Contact Us), with its fields named, labeled, grouped and explained, and release and expiry dates as dates. Menus, people and files move too. Pages and design come next. What you need, and what moves.

October 1, 2026: version 0.0.5

  • Webflow is available to everyone. Choose Webflow on the Source step. The connect page lists each permission the token has. A Redirects page on the Transform step shows what the tool found and takes Webflow's export. What people sent through the site's forms moves, as a table for each form. The sitemap and robots.txt move. The checklist names the jobs a Webflow site needs: its other domains, its Adobe Fonts kit, forms to rebuild, search engines, and keeping the Webflow site until the new one has run cleanly. Moving a Webflow site.
  • A page that does not answer is a page not checked. SITE, CONTENT, ADDRESSES and REDIRECTS ask for a page again when the connection fails. A page that still does not answer fails the check and is counted, so a network that drops part way through a verification can no longer shrink what a check counts, or pass a check that read nothing.
  • Webflow collection pages and lists, in beta. Each collection's page becomes one Insites page that reads its item's row from the table, at the same addresses, and answers 404 for a draft, an archived item or a made-up address, as Webflow does. Every collection list reads its table too, with the filter, order, limit and pages the live site shows, so an item an editor adds shows up. The tool learns each template by lining up the item pages Webflow publishes, and checks it against every one of them, word for word, before it is used. How it works.
  • Webflow redirects, found for you. On an Enterprise plan the tool reads a site's redirects from Webflow. On any other plan it finds them itself, with nothing to export: it asks the live site about every old address the Internet Archive has seen on the site's domains and every link to a page the site no longer publishes, and keeps each one that sends a visitor somewhere else. A chain becomes one hop. Webflow's export is still the complete list, and a list you give wins. How it works.
  • A Webflow site's other domains. With Sites access, a link to any of the site's domains is made relative, and the inventory counts the domains to point at Insites when the site goes live.
  • A Webflow site whose shop was never set up connects with every permission, instead of stopping at the Ecommerce check.

September 30, 2026: version 0.0.4

  • Webflow pages and design, in beta. Every page a Webflow site publishes moves to the same address, read from the live site, with its title, description and sharing tags, and every file it loads (styles, scripts, fonts, images and their phone-sized versions) is copied and named with asset_url, so nothing loads from Webflow. Redirects from Webflow's export become redirects on the new site, and the place to give the tool the export comes next. Three checks come with it: CONTENT (every page says the same), ADDRESSES (nothing loads from the old site) and REDIRECTS.
  • Webflow, in beta. A Webflow site's CMS moves through a site API token: every collection becomes a Data table set up the way the admin shows each kind of field, every item a row (drafts and archived ones marked), every image and file a copy on the new site, and the text that named Webflow's file host now names the copy. Each item keeps its Webflow id, so a final sync updates rows instead of adding them. It becomes available to everyone once pages and design move too. How to make the token, and what moves.
  • Two new checks. REFERENCES checks that every reference points at a row that is there, and SOURCE reads the source again at the check and compares every row with it as it is now.
  • A Connectors section in the docs, with every source the tool moves from, its status and the key it needs.
  • Tables keep how they are set up. A column's label, form control, dropdown options, required flag, group, order, tooltip, what it points at and its default now move with it, so a table reads in the admin as it did on the source, not as a list of raw names. A table the destination already has is set up the source's way, and a rollback puts it back. A new check, SCHEMA, checks every table and column.
  • Everything the Insites admin made moves. A CMS collection's pages, Site Manager pages, form emails, API endpoints and your template's files live in ins_ folders, which the tool had treated as the platform's. They now move and are checked like the rest of your code.
  • People keep their external id when the load creates them, and a person the destination already has is given the source's, so CRM rows find them.
  • A check that everything is accounted for. INVENTORY counts everything the source holds, item by item, and names anything that is neither on the destination nor left behind with a reason.
  • A check for your asset files, by path and size.
  • A confidence score on the Verify result, in the email and in the report: how much of what should be on the destination a check proved is there, with its denominator.
  • Every page is checked and photographed. The screenshots carry on in the next step instead of stopping at a time limit.

September 29, 2026: version 0.0.3

  • Stop a migration at any point. A Stop button on every working run. It stops at the next safe point, keeps what was written, and offers to carry on or roll back.
  • Every button shows it is working and cannot be pressed twice, and a press on something already done says so kindly.
  • The log follows the newest line, and the progress line says what the load is doing, in rows out of the total. A pause says when it carries on.
  • Every status explained. Statuses lists each one in its color, with what it means and what to do. A run a person stopped now reads Stopped, one that hit a problem reads Failed, and one waiting out the destination reads Paused.
  • Emails you can read at a glance. What happened in a few words, what to do, and the checks with their marks, problems first.
  • A form whose table stays behind is a decision on the plan, instead of stalling the load.
  • A shorter, clearer wizard. Seven steps (Source, Destination, Transform, Plan, Load, Verify, Finish), each split into short pages. A footer with Back, where you are and the next thing to do, dots that show progress, and a list of the steps down the side.
  • Long lists are a count and a sample. Sections open and close, long tables filter and download as CSV, and the plan no longer lists every person by email.
  • Checks in plain words, such as "Every row matches the source", with the technical name underneath.
  • Links that open the right page, from the address bar and from every email, and the time left while a run works.
  • The migrations list folds final syncs under the migration they follow, with status filters and a search.
  • Dark mode, following your computer's setting.
  • Sign in without a password. Enter your email address and the tool emails you a link that works once. Insites staff can still sign in with Insites Console.
  • Invitations that arrive. Adding someone to an agency emails them a sign-in link, and the People list shows whether each invitation went and when each person last signed in.
  • Every check is kept. Checking a migration again never replaces the earlier result: the Verify step and the report list them all.
  • Exactly what differs. A failed check shows each row's fields, or each file's changed lines, side by side, with a button to copy it again from the source.
  • Migrations and New migration are separate items in the menu.

September 28, 2026: version 0.0.2

  • Everything moves. People's profiles (CRM details, administrator settings), SMS and API call notifications, the CRM's import log, webhooks (switched off for the move), the store's settings and every constant by default. What does not move is listed with the reason.
  • The whole instance on the connect page, by module, with each part's status and every module's version on both sides.
  • Passwords can move with the people the load creates.
  • One-click fixes on the plan, a list of the decisions your changes settled, and an approve button that says why it is waiting.
  • Liquid v6 refuses, fixed for you where there is an equivalent, and the old instance's addresses rewritten.
  • Signed-in checks with test accounts, and screenshots of every page on both instances.
  • A PDF report of every decision, kept in the tool after the source is gone.
  • Next steps worked out for each site, with tasks written by AI.
  • Nightly sync during a rehearsal, and a 48-hour watch after cutover.
  • A migration waits out an instance that stops answering and carries on, instead of failing.
  • Every step can be opened again to see what happened there.

September 27, 2026: version 0.0.1

  • First release: extract, transform, load and verify for Insites v5 to v6, dry runs, rollback, final sync and cutover, agency workspaces, the secrets check and partial moves.