What it costs, and what moves the number.
Migrations start at $5,000 and are priced once, after the assessment, before any work begins. What decides where a particular site lands is below, in the order it matters.
Why there is no price list
The page count is the wrong question.
Every request for a migration quote arrives with a page count, and it is close to useless on its own. What a migration costs is decided by how many distinct things have to be rebuilt and how much of the site is doing work the platform used to do. Two sites with four hundred pages each can differ by a factor of five, and the difference is visible in about twenty minutes of looking.
That is what the assessment is for: it looks at your site and reports what is actually there, so the number is based on your site rather than on an average.
Cost drivers
Seven things decide the estimate.
-
Number of templates, not number of pages
Four hundred pages built from six templates is six things to rebuild. Forty pages each adjusted by hand is closer to forty. 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.
-
Interactions and motion
Webflow interactions do not export as anything you can run. Rebuilding a scroll-linked sequence faithfully takes real time; deciding it was never worth its weight takes a conversation.
-
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.
What is not in it
Scope stated in both directions.
- A redesign. If the design changes, that is scoped separately and I would rather do it after the move than during it.
- New content. Existing content is migrated; writing new pages is a different job.
- Hosting and platform costs, which go to whoever you host with rather than to me.
- Ongoing development after launch, which is either the monthly retainer or nothing.
The cheapest migration is the one that moves the site as it is and changes nothing else. Every addition is worth doing on its own merits, and worth doing separately.
The honest version
Some sites should not pay for this at all.
If your team edits layouts visually every week, your CMS needs are modest and the site is working, a migration costs you money and takes away something you use. That is a real outcome and I would rather say so before you spend anything. The stay or move decision is written out properly, including the cases where staying wins.
Reach out and see if we are a good fit.
Currently booking two to four weeks out.