What would it take to move this site?
Scan the site, correct what the scan got wrong, and take away a scope brief. It gives you a starting figure and the questions that decide the rest. No email, and nothing is sent until you send it.
Your migration scope
See what the move involves.
Scan the site, or start with what you know. Review what came back, describe how your team works, and take a scope brief into the conversation.
No scan yet. Scan the site above, or fill this in by hand.
- Sitemap entries
- Unknown
- Platform detected
- Unknown
- Third-party script hosts
- 0
- Sitemap sections
- 0
- Locales declared
- 1
The scan can supply platform signals, sitemap counts and script hosts. Layouts, CMS records and historical redirects need confirmation.
What moves the number.
The scan sees how big the site is and roughly what shape it is in. These are the things that decide where inside a range it lands, in the order they matter.
Number of templates, not number of pages
Two sites with the same page count can differ by a factor of seven, because what gets rebuilt is the number of distinct templates rather than the number of pages rendered from them. This is the single biggest variable, and it is the one people are most often surprised by, in both directions.
How much the CMS is doing
A blog with a title, a body and an author is a short job. Collections with multi-reference fields, nested relationships and items that drive layout are a content modeling exercise before they are a migration.
Custom code already on the site
Custom code is usually the reason a team is leaving, and it is rarely portable as written. Some of it is a few lines that become a component. Some of it was compensating for a platform limit that no longer applies, and the right move is to delete it.
Integrations, counted honestly
Forms, analytics, consent, CRM, chat, scheduling, payments. Each one is re-established and tested separately. Five integrations is not five times one integration, but it is not one either.
URL surface
A hundred URLs is an afternoon of mapping. Several thousand, with historic paths, paginated archives and campaign URLs nothing links to any more, is its own workstream.
How closely the design is kept
Rebuilding the existing design as it stands is the cheapest path and usually the right one. Redesigning while migrating is two projects, and running them together is how both get worse.
Want to know what is wrong with the site instead?
The free site check reports on speed, structure, search and what a crawler can read, and separates the findings that are yours to fix from the ones that belong to the platform. It is a different question from this one.
Run the site performance checkMigration questions, answered.
How much does it cost to migrate a website?
Here, from $5,000, fixed once the scope is agreed and before anything starts. An agency rebuild of the same site is commonly quoted between $2,500 and $8,000 for a brochure site, $8,000 and $25,000 for a mid-size business site, and $25,000 upward for a large content or commerce site. Those are estimates of the market rather than quotes from anyone, and what decides where a particular site lands is above.
How long does a migration take?
Two to four weeks for a typical site, then a week of watching what the old addresses return. What stretches it is rarely the rebuild: a redesign running alongside the move, content being rewritten while it migrates, or a CMS decision still open when the rebuild starts will each add more than the page count does.
Will I lose my search rankings?
Not if every address that existed keeps working. The usual cause of a drop after a migration is a redirect that was never written, or a chain of them that resolves four hops later. The addresses are mapped from analytics and Search Console rather than from a crawl of the current site, because a crawler only finds what the site links to now.
How accurate is this estimate?
It is a starting figure, not a quote, and it says so. The scan establishes how many addresses the sitemap declares and roughly how they are grouped. It cannot see your CMS records, your historical redirects, or what your custom code is doing, and those are three of the things most likely to move the number. Everything it cannot establish is listed as a question rather than assumed to be zero.
What happens to the site you scan?
The address is read, not saved. There is no database behind this, the scan keeps no log of it, and no copy of anything reaches me. Your answers stay in the page until you choose to carry them into the inquiry form yourself.
Reach out and see if we are a good fit.
Currently booking two to four weeks out.