Benchmark
Traffic, rankings, conversions and backlinks per URL and per template, captured before anything moves.
MIGwebsite migration services
Website migration services with a QA trail you can audit.
Founcy Solutions' website migration services protect the rankings, traffic and leads you've earned when you change CMS, domain, URL structure or design. Every legacy URL is weighted by its clicks, backlinks and conversions, mapped one-to-one, tested on staging, and watched daily after launch.
- value-weighted redirect map
- staging crawl diff
- agreed rollback trigger
- legacy URLs mapped one-to-one to new URLs with 301s
- unmatched URLs (404) flagged and fixed before launch
- traffic line steady through the cutover
1:1 permanent redirectsno chains404s fixed before launch
definition
What are website migration services?
Website migration services manage the search side of any big change to a site: a new CMS, a new domain, HTTPS, a new URL structure, a redesign, or several sites merging into one. The work is to carry every page's search equity across. That means benchmarking what each URL earns today, mapping it to its closest new equivalent with a permanent redirect, keeping content and metadata intact, and checking after launch that search engines are crawling and indexing the new site as planned. Migration and redesign support is already part of Founcy Solutions' technical SEO work. This service makes it a dedicated engagement.
- Migration types
- CMS, domain, HTTPS, URL structure, redesign and site merges
- Core deliverable
- A value-weighted redirect map, one-to-one wherever possible
- Verification
- Staging crawl diff before launch; logs and Search Console after
- Redirect lifetime
- At least a year, per Google's guidance, and longer for linked URLs
- Case study
- Sana's Beauty Studio, Walthamstow: a redesign took load time from 7s to 1.4s, and quote enquiries tripled in month one
sound familiar?
A migration is coming. Is search in the plan?
Tick what applies. We'll bring it into the scoping call.
Tap anything that sounds familiar.
Get migration support early →what's included
SEO website migration, start to stable.
The search workstream runs alongside whoever builds the new site: your team, an agency, or our own developers.
URL inventory
Every URL from crawls, sitemaps, analytics, Search Console and backlink data, not just the CMS export.
Redirect map
Weighted by value, one-to-one wherever possible, with no chains and nothing dumped on the homepage.
Parity checklist
Content, headings, metadata, schema and internal links checked for every key template.
Staging QA
A staging crawl diffed against live, with rendering checks and a go/no-go sign-off.
Launch-day run
Redirects live, noindex removed, sitemaps submitted, and Change of Address filed where it applies.
Post-launch watch
Crawl errors, indexing, server logs, rankings and conversions, checked daily at first.
Migration report
What was found, what was fixed and what's still open, with evidence for each.
verified, not promised
"No traffic loss" is a promise. We show the method.
Some short-term fluctuation is normal while search engines reprocess a moved site. Large, lasting losses almost always trace back to something on the left.
success measured by: gut feel
RedirectsBulk rules, leftovers sent to the homepageOne-to-one mapping, prioritised by each URL's traffic, links and conversions
Content parityCopy, FAQs and internal links quietly dropped in the redesignA parity checklist per template, signed off before launch
StagingStaging indexed, or noindex left on at launchStaging locked down, and the launch checklist clears it
Verification"Traffic looks okay, I think"A before-and-after crawl diff, plus logs showing Googlebot on new URLs
AI answersNot consideredPages cited in AI answers stay reachable, with equivalent content
RollbackNone, so issues get fixed liveA rollback trigger agreed before cutover
how it works
Planning takes longer than the launch.
That's on purpose. Most of the risk is removed before cutover day.
- 01
Discover & benchmark
Scope, migration type, risks, and baselines for traffic, rankings and conversions by URL and template.
→ benchmark report - 02
Map
URL inventory, then the value-weighted redirect map and the content and metadata parity plan.
→ redirect map, parity plan - 03
QA on staging
A crawl diff against live, rendering checks, and analytics and tag checks before anyone says go.
→ go/no-go sign-off - 04
Launch
A controlled cutover run from the checklist, with the rollback trigger agreed in advance.
→ launch log - 05
Monitor & stabilise
Daily, then weekly checks: fix residual 404s, follow indexing and logs, and report back.
→ migration report
migration checklist
Check your plan against ours.
Tick what your current migration plan already covers. Anything left unticked is where traffic usually goes missing.
Before launch
Launch day
After launch
Start ticking what your plan already covers.
Fill the gaps with us →migration risk scorecard
How risky is your migration?
Risk, and cost, scale with four things. Set them for your project and see where it lands.
tools
The instruments behind the evidence.
// crawl & diff
Screaming FrogSitebulbList-mode recrawlsRendering checks
// search engines
Search ConsoleChange of AddressURL InspectionBing Webmaster Tools
// value data
GA4Server log analysisAhrefsSemrush
// redirects
Redirect map databaseAutomated redirect testsnginxCloudflare rules.htaccess
keep exploring
Related services.
SUP
Website support
Ongoing support and management for the site after it moves.
Explore → HSTHosting & maintenance
Managed hosting for the new platform, monitored for crawl health.
Explore → WPMWordPress maintenance
Moving to WordPress? Keep it updated, secure and fast after launch.
Explore → ENTEnterprise dev support
Large replatforms that need engineering capacity alongside SEO.
Explore →faq
Website migration questions.
Some short-term fluctuation is common while search engines reprocess the site. Large or lasting losses usually trace back to missing redirects, lost content or blocked crawling, and the QA process is built to catch those before launch and in the days right after it.
It depends on the number of URLs, the type of migration, how much content changes and your development dependencies. Benchmarking, mapping and staging QA usually take longer than the launch itself, and that's where the risk gets removed.
Use permanent redirects, 301 or 308, for permanent moves; Google treats both as permanent signals. Avoid chains, and send each URL to its closest equivalent page, never to the homepage by default.
Google advises keeping them for at least a year. Longer is safer, especially for URLs with backlinks from other sites, which keep sending visitors and signals long after the move.
The search workstream (benchmarks, mapping, QA and monitoring) can run alongside any development team. If you need build capacity too, development can be added to the same engagement.
It depends on URL count, migration type (a domain, CMS and redesign change together is the most complex), the number of languages, and how long you want post-launch monitoring to run. The risk scorecard above uses the same factors.
Treat them like your highest-value URLs: keep them reachable through one-to-one redirects, keep the content equivalent, and keep it server-rendered so crawlers that don't run JavaScript can still read it.
before you move
Move the site. Keep what it earned.
Send the site that's moving. We'll benchmark it, size the URL inventory and tell you where the risk sits before you commit to a launch date.
quote within 24 hours · one-to-one redirect maps · rollback trigger agreed up front