Your move to AI-native. Handled by ZINC.
Bring your website into an AI-native environment with an experienced team handling the migration, our governance platform, Dispatch, providing control, and your team prepared to take over.
In short
An AI website migration moves your pages, content, and search equity onto a codebase your team updates by asking its own AI agent. The work that protects you comes first: every URL inventoried, every redirect mapped, every title, form, and integration carried over and tested.
Your current site stays live until the new one checks out. From the first day after launch, Dispatch governs every change the agent makes.
25+ years of strategy, design, and digital delivery for brands including:
From your current CMS to your next chapter.
Keep the design and content that work. We handle the technical transition and prepare your website for the way your team wants to work.
Your design and content.
Recreate your agreed layouts, move your pages and content, and check the experience across desktop and mobile.
Your search foundations.
Map URLs, metadata, internal links, and redirects, with launch checks and a plan to monitor search performance.
Your business connections.
Review forms, analytics, CRM connections, and other integrations, then rebuild or reconnect what your website needs.
Your team’s new workflow.
Configure hosting, your chosen AI agent, and Dispatch, then guide your team through reviewing and publishing its first changes.
Pick the move you are planning.
Each path covers what moves, what each platform feature becomes, and when staying put is the smarter call.
Not sure what you have? Run the free migration planner > Moving from Drupal, Sitecore, or a custom CMS? The method is the same. Tell us what you are on >
Nothing gets designed until every URL has a plan.
The same six steps on every move, written down while we moved our own website. The boring part comes first, because the boring part is what protects your traffic and your leads.
- Step 01
Inventory every URL.
We crawl the live site and list every page by template before anything is designed or built.
On our own moveOur site: 49 live URLs across six templates, each with a destination before a line of code.
- Step 02
Keep the URLs.
Same paths, same slugs. An address only changes when a 301 redirect is in place for it.
On our own move44 kept their exact address. 5 retired pages got 301s. Our highest-traffic page never moved.
- Step 03
Export everything.
CMS content, every file on the old platform’s CDN, and the rendered HTML of every page as the reference copy.
On our own move549 files moved off the old CDN. 4 CMS collections, 45 items, imported and checked.
- Step 04
Parity first. Then improve.
The first version is a faithful copy: same pages, same copy, same metadata. Changes come after sign-off, so any traffic shift has one cause to look at, not ten.
On our own moveOur first complete build took one day, compared page by page against the original by screenshot.
- Step 05
Prove the business paths.
Forms, CRM delivery, notifications, analytics, and consent are tested end to end, from the visitor’s click to the right person’s inbox.
On our own moveLesson we learned: a form that saves a lead is not a form that tells anyone. We test to the inbox now.
- Step 06
Govern, launch, and watch.
Dispatch is connected before the agent touches production. Redirects go live at cutover, the sitemap is submitted, and 404s and indexing are watched closely.
On our own moveSince our launch: 36 reviewed changes in six weeks, each one previewed before release.
We moved our own website first.
In August 2026, wearezinc.com moved from Webflow to Next.js on Vercel, using the same six steps we use for clients. Webflow served us well, and we still build on it for enterprise teams. We moved for one reason: how fast the site could change.
- live URLs kept or redirected
- 49 of 49
- files moved off the old CDN
- 549
- to the first complete build
- 1 day
- reviewed changes in the first six weeks
- 36
| Template | URLs | Outcome |
|---|---|---|
| Blog posts/post/… | 16 | All kept |
| Solutions pages/solutions/… | 10 | 9 kept · 1 redirected |
| Core pages/, /about-us, /work … | 10 | 7 kept · 3 redirected |
| Case studies/work/…, /thomabravo | 6 | All kept |
| Partner pages/partners/… | 4 | 3 kept · 1 redirected |
| Legal pages/about/… | 3 | All kept |
| Total | 49 | 44 kept · 5 redirected · 0 lost |
About the same, and that is the point.
Our homepage was already light on Webflow: about 0.7 MB and 38 requests on first load. On Next.js it is 0.64 MB and 35. If a migration pitch leads with page weight, ask what your site weighs today. The bigger gain is the pace of change.
Test the form all the way to a person.
After launch, our forms saved every lead to the CRM. But the CRM does not send alerts for contacts created through its API, so nobody was told. The leads were safe and unseen until we caught it. Notification is now a launch check on every migration, tested to the inbox.
How we measured page weight: homepage first load at 1440px, cache disabled, median of three runs on October 15, 2026. Webflow figures load the archived August 12 capture of the live site.
A website move. A lasting partnership.
Your website carries your brand and supports your business. Work with a team that understands both, with 25+ years of experience in strategy, design, and technology.
Control comes with the setup.
Our governance platform, Dispatch, provides visibility into AI website work. We configure your review and approval workflow and establish a recovery process for supported changes.
Meet Dispatch >Support beyond the switch.
Run the site with your own team, work alongside ZINC, or have us manage ongoing improvements, from brand and campaigns to SEO and AEO.
Explore Our Work >Send us your website. We’ll map the next step.
Tell us what you’re working with and when you’d like to move. We’ll review your website, clarify the requirements, and prepare a scoped proposal.
Migration scope and recommended setup.
Delivery timeline and launch responsibilities.
Implementation and ongoing costs.
A few practical questions.
Yes. We review your content, functionality, and integrations to determine the right architecture and migration scope. Features tied to your CMS may need rebuilding or an alternative service.
Explore AI-Native Websites >No. We can migrate with your agreed design and content intact. If you want changes, we scope those separately so you can decide how much to take on.
Losing what your site has already earned. Search traffic usually slips after a move for three reasons: URLs that break, page signals that get dropped, and crawl problems after launch. That is why the URL inventory and redirect map come before any design work, and why we watch 404s and indexing closely in the weeks after cutover instead of waiting for a monthly report.
Less time than most teams expect. We built the first complete version of our own website, with every page checked against the original by screenshot, in a single day. The calendar goes to the work that protects your business: forms and CRM connections, redirects, analytics, and your team’s review. A typical marketing site moves in weeks, not months. Large content libraries and complex integrations take longer, and your assessment gives you a dated plan before you commit.
See how this site runs today >Two very different jobs both get called a migration. Copying content onto a new platform is cheap and risky. A governed rebuild, with every URL mapped, every form and integration tested, and Dispatch configured, is the job that protects your traffic and leads, and it is the only kind we do. Cost follows the number of page templates (not pages), content volume, integrations, and how much you want to improve along the way. Your proposal separates the one-time migration fee from hosting, agent usage, Dispatch, and any ongoing support.
Your existing site stays live during the build. We plan URL continuity, redirects, and technical checks before cutover, along with post-launch monitoring. Search rankings can fluctuate, so we do not promise unchanged rankings.
Ownership, repository access, hosting accounts, and third-party services are documented in your proposal and handover. We train your team on the agreed workflow and identify where specialist support is needed. Ongoing ZINC support is an option.