The site outgrew the deploy button.
Netlify is a good place to put a site and a poor place to leave one nobody can edit. Most of the work we do here is a migration: the marketing pages onto a CMS the team can use, the redirects and edge functions into something owned, and a clear line between what belongs on the host and what belongs in the CRM.
Every page change goes through an engineer.
The site ships fine. That was never the complaint. The complaint is that a headline, a pricing table or a new landing page is a pull request, a review and a queue — so marketing stops asking, and the site stops changing.
A headline should not need a release.
NetlifyWhat the move actually involves.
The line between host and CRM
Marketing pages, forms and gated content move to the CMS where attribution already lives. The app, the docs and anything with a build step stay where they are, on a subdomain or a proxied path.
Templates a marketer can fill
The existing components rebuilt as modules with editable fields, so a new page is composed rather than coded. No developer in the loop for a launch.
Redirects carried over intact
The _redirects and netlify.toml rules read line by line, splats and query rules included, then re-expressed on the new host and tested against the live URL list before cutover.
Edge functions given an owner
Geo routing, A/B splits, header rewrites and auth shims usually written by someone who has since left. We inventory what each one does, keep the ones that earn it, and retire the rest.
Forms that reach the pipeline
Netlify Forms submissions land in a dashboard nobody opens. We replace them with forms that create records, fire workflows and carry the source through to the deal.
Performance and search held flat
Core Web Vitals measured before the move and after, canonical tags and sitemaps mapped one to one, so a ranking move afterwards can be attributed instead of guessed at.
Inventory, split, rebuild, cut over.
Inventory
Every route, redirect, function, form and environment variable listed against what it does and who last touched it. Most of the risk in a migration is in the things nobody documented.
Split
The decision on what moves to the CMS and what stays on the build, written down with the routing that makes both live under one domain.
Rebuild
Templates and modules built on staging, content moved page by page, redirects loaded and tested while the old site is still serving traffic.
Cut over
DNS moved at a quiet hour with the redirect map verified, then a watch on 404s, form submissions and search console until the numbers settle.
The redirects are the whole migration.
Years of campaign URLs, old blog paths and vendor links point at routes that only exist as rules in a config file. Miss a rule and the traffic does not error loudly — it lands on the wrong page, or on nothing, and shows up weeks later as a slow decline nobody can attribute.










Tell us what marketing cannot edit.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.