Migrations Are Planned as a Technical Move and Lost in the Content Inventory
Everyone plans the platform, the design and the launch date. Almost nobody starts by listing what is actually on the current site — and that list is always longer than anyone expects. The landing page built for a campaign three years ago. The PDF linked from a client’s email signature. The form that posts to an address nobody remembers configuring. Those are what go missing, and they go missing quietly.
No credit card required · 30-minute call · No obligation to sign up
Six things that break and are not on the plan
The technical move is the part that gets rehearsed. These are the parts that get discovered, usually by a customer.
- Pages nobody knew existedCampaign landers, old offers, orphaned drafts
- Files linked from outside the sitePDFs in email signatures and client folders
- Forms that stop sendingSilently · nobody notices for weeks
- Email breaks with DNSSame records · different consequence
- Tracking resets to zeroAnd nobody can compare before with after
- Integrations point at the old hostCRM, booking, payment webhooks
The third row is the one that costs money without ever producing an error. A contact form that submits successfully and delivers to nowhere looks completely fine from the outside — the customer sees a thank-you page and waits for a reply that is not coming. Nobody reports it, because the people who would report it are the ones who never heard back. Testing every form end to end, on the live site, after cutover, is fifteen minutes and it is the highest-value quarter of an hour in the entire project.
The inventory is the migration — everything else is execution
A migration plan that starts with the new site is already behind. It starts with a complete list of what exists now: every URL, every file, every form destination, every integration pointing at the current host, and every place outside your control that links to something on it. That list takes a day to assemble and it is the document the whole project is run from. Without it, the launch checklist is a guess about a site nobody has fully seen.
We are able to be specific about this because we did it to ourselves. This site replaced one with 1,630 URLs carrying 50,541 impressions, and the whole migration is written up at /portfolio/case-study/own-migration/ including what the audit turned up. Zero URLs were left to 404 at launch. That is not a claim about skill; it is what having the inventory first buys you.
The second half is rehearsal. A migration should be performed at least once somewhere that does not matter — a staging copy, with the real content, tested by people who use the site rather than by whoever built it. What that catches is never the thing that was worried about. It is the search page that returns nothing, the PDF that moved, the checkout step that works everywhere except one browser.
And there needs to be a way back. Not a theoretical one: an actual written sequence, agreed before launch, that says who decides to roll back, what gets reverted, and how long it takes. Most migrations never use it. The ones that need it need it inside the first hour, which is the worst possible time to be inventing a plan.
- ✓Inventory before anything else — Every URL, file, form destination and integration. A day of work, and the document the project runs from.
- ✓Test forms after cutover, live — A form that submits and delivers nowhere looks perfect. Nobody reports it — the people who would never heard back.
- ✓Rehearse on staging with real content — What it catches is never what you were worried about. That is the point of doing it.
- ✓DNS moves email too — The same records carry both. Mail is the failure people notice fastest and forgive slowest.
- ✓Write the rollback down — Who decides, what reverts, how long. Needed within the first hour if at all.
A contact form that submits successfully and delivers to nowhere looks completely fine. The only people who could report it are the ones still waiting for a reply.
What a migration actually involves
Six things. The first one is a day of work and it determines whether the other five are planning or guessing.
The Full Inventory
Every URL, file, form destination and integration on the current site, including the pages nobody remembers and the PDFs linked from outside it. The document everything else is run from.
Content and Data Migration
Pages, media, users and records moved with their relationships intact. This is the slow part of every migration and the one most consistently underestimated when the project is quoted.
Integrations and Forms
CRM, booking, payment webhooks and every form destination repointed and tested end to end on the live site — because a form that fails silently is the failure nobody reports.
DNS and Email Cutover
Sequenced so mail keeps flowing. The same records carry both the site and the email, and mail is the failure people notice fastest and forgive slowest.
Rehearsal on Staging
The whole move performed once with real content, tested by people who use the site rather than by whoever built it. What it finds is never what was expected, which is the reason to do it.
A Written Rollback
Who decides, what reverts, and how long it takes — agreed before launch. Rarely used, and when it is needed it is needed inside the first hour.
What clients say
Real clients, quoted in their own words — published with their permission.
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“It was a pleasure working with Ghalib and his team.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Website Migration
The method doesn’t change by market. What it’s pointed at does.
Audit & Discovery
What the current site earns, where it leaks, what your competitors do better, and what the new one must achieve. Ends in a written scope and a fixed price — not an estimate that grows.
Structure & Design
Sitemap, wireframes and user journeys agreed before decoration, then a design system applied consistently. You approve the shape before we make it beautiful.
Build & Test
Front end, back end, CMS and integrations, on a staging site you can see from day one. Tested on real devices, real screen readers and real slow connections.
Launch & Improve
Redirects verified, analytics connected, handover recorded — then we look at what real visitors actually do and fix what the design assumed wrongly.
Honest, No-Nonsense Commitment
The price we quote after discovery is the price you pay — if we underestimated the work, that is our problem, not a change request. And on any rebuild, if organic traffic drops because of something we did at migration, we fix it at our cost, however long it takes.
Website Development pricing for Website Migration, in USD
Quoted per migration, and driven by how much content moves rather than by how the new site looks. The inventory is quoted separately and can be bought on its own — several clients have taken just that, then done the move themselves, which is a perfectly reasonable outcome.
Inventory only
The document, yours to act on.
- Full URL, file and form inventory
- Integrations and external links mapped
- Risk list, yours to use with anyone
Full migration
Inventory, move, rehearsal and cutover.
- Everything in Inventory, plus the move
- Content, media and data migrated
- Staging rehearsal & written rollback
- Optional: bundle in SEO so the redirect map is handled too
Complex replatform
Large catalogues or many integrations.
- Dedicated senior developer
- Multi-system integration cutover
- Phased launch and post-launch support
- Optional: combine all 4 services for full-funnel growth
Every plan is scoped around your market — get a free audit and we’ll recommend what fits, priced in USD.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- A fixed price, agreed before we startQuoted after discovery, not estimated on a call. If the work takes longer than we thought, that is our risk — the price does not move unless you change the scope.
- 50% to begin, 50% at launchNo large upfront payment held for months, and nothing owed until the site is live and you have seen it working.
- You own everythingDomain, hosting, code repository, design files and content — all in your name from day one, and still yours if we never work together again.
- No proprietary lock-inStandard, widely-used technology only. Any competent developer can take the site over, and nothing stops working because you stopped paying us.
- Two rounds of revisions per stageIncluded at wireframe and design stage, where changes are cheap. Beyond that, or after sign-off, changes are quoted before any work starts.
- 30 days of support after launchBugs and small tweaks included as standard. A care plan afterwards is optional, never automatic, and cancellable with 30 days’ notice.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
Website Migration Website Development questions, answered
Related Website Development pages
Same service, different angle — by market, by discipline and by platform.
Ready to move without losing the things nobody listed?
Free 30-minute audit · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.