Moving a website can mean transferring the same site to a new host, rebuilding it on another platform, or changing its domain and structure at the same time. Those are different projects, and their quotes should look different.
Before comparing prices, establish what needs to move, what needs to be rebuilt, and what cannot afford to stop working. A low transfer fee tells you very little if it excludes your forms, integrations, redirect planning, or launch testing.
This guide breaks down the main migration costs and shows you what to ask for in a quote, so you can budget for the move rather than the surprises afterward.
How much does website migration cost?
| Migration scope | Published price reference | How to interpret it |
|---|---|---|
| Same-platform host swap | $300 to $1,500 | Project Cost Estimator’s range for a same-platform host swap, not every hosting migration. |
| Simple brochure-site agency migration | $2,500 to $8,000 | Ploy’s published agency estimate. Confirm the page, design, and testing scope. |
These third-party estimates describe different types of projects. They are not WFpulse prices or directly comparable quotes. Use them as starting points, then compare what each proposal actually includes.
1. What kind of migration am I buying?
Start by naming what changes. A hosting migration moves an existing site to different infrastructure. A CMS migration or platform migration transfers content and rebuilds the site in another system. A domain migration changes its web address. A website merger combines sites and requires decisions about overlapping content and destinations.
A website redesign can accompany any of these, but it is not automatically included. Keeping the same visual design on a new platform can still require rebuilding templates, CMS collections, navigation, and interactive features.
For a move to Webflow, our Webflow development services cover CMS architecture, template builds, integrations, and migration work.
Write a one-sentence scope before requesting prices: “Move our existing site to a new host while retaining the domain, URLs, design, and functionality.” If you also want a new platform, rewritten service pages, or a different URL structure, name those separately.
2. What does the estimate include and exclude?
A useful estimate describes deliverables, quantities, responsibilities, and how you will confirm the work is complete. “Migrate website” does not tell you whether someone will transfer blog images, reconnect a booking tool, map changed URLs, or verify that inquiries reach your team.
Hypothetical scope comparison: Hosting-only move versus platform rebuild
Here is a hypothetical comparison for a small-business website with service pages, a blog, a quote form, and a booking integration. Actual deliverables should be agreed in your proposal.
| Scope item | Hosting-only move | Platform rebuild | Clarify in the quote |
|---|---|---|---|
| Site and content | Back up and transfer existing files and database, where applicable. | Transfer agreed pages, posts, images, and files into the new CMS. | Content quantities; responsibility for cleanup and missing assets. |
| Design and templates | Retain the existing design. | Rebuild agreed templates and mobile layouts. | Recreating the design or creating a new one? |
| Forms and integrations | Check compatibility, reconnect services, and test delivery. | Rebuild or replace agreed connections and test workflows. | List each form, booking tool, CRM connection, and custom script. |
| URLs and technical SEO | Retain URLs; check redirects and indexing settings. | Complete redirect mapping for changed URLs; review metadata and indexing. | Who prepares, implements, and tests redirects? |
| Deployment | Coordinate DNS, HTTPS, backups, and rollback readiness. | Launch the rebuilt site with the same checks. | Launch owner; email and domain access dependencies. |
| Testing and handover | Check agreed functions and tracking. | Check templates, content, integrations, redirects, and tracking. | Completion tests, handover materials, and the period for fixing migration-related problems. |
| Optional work | Redesign, copywriting, new features, and email migration. | New branding, copywriting, extra features, and broader content strategy. | Include only when agreed; price separately. |
Also separate the project fee from recurring hosting, platform subscriptions, paid apps, software licenses, and ongoing Webflow maintenance. State who buys and owns each account. Define the period for fixing migration-related problems separately from future changes.
3. What makes my project more expensive?
Page count matters, but template variety, content quality, and functionality often explain more of the estimate. Hundreds of consistently structured posts can be simpler to transfer than a smaller site full of unique layouts and undocumented code.
- Content cleanup: Missing images, inconsistent fields, duplicate pages, and manual formatting add work beyond transferring records.
- Custom functionality: Calculators, memberships, product options, search filters, and customer portals require their own implementation and testing.
- Integration dependencies: Booking tools, payment systems, CRM connections, and each API integration need named owners, access, and realistic test cases.
- E-commerce data migration: Define which products, variants, customer records, and order history must move, and how their accuracy will be checked.
- Structural changes: A new domain, consolidated pages, or revised URL structure adds mapping and validation work.
- Launch constraints: Tight deadlines, multiple approvers, and limited downtime windows increase coordination and contingency needs.
For WFpulse, the practical priority is identifying what the website must continue doing for the business. A service page, quote form, or booking flow needs a specific test to confirm it works, not just a visual check.
Ask vendors to distinguish known work from allowances and unresolved dependencies. An unknown integration should trigger investigation or a defined budget allowance, not an assumption that everything is covered.
4. How do I compare quotes fairly?
Give every provider the same inventory and requirements. Include pages and templates, CMS records, integrations, files, current URLs, and the changes you actually want. Otherwise, the cheapest estimate may simply describe the smallest project.
A hosting-only quote and a platform-rebuild quote are not competing prices for the same job. Compare deliverables before comparing totals.
Then compare proposals against the same questions:
- What quantities, templates, and features are included?
- Who supplies content, credentials, approvals, and third-party access?
- Are redirects, analytics, functional testing, and deployment separate deliverables?
- What counts as extra work, and how is it approved and billed?
- When are payments due, how will you confirm the work is complete, and what support follows launch?
Fixed-price work is easier to evaluate when the scope is settled. For hourly work, ask for an estimated effort range, reporting arrangements, and a spending limit that requires approval to exceed. In either case, separate required migration work from optional improvements.
5. What must be tested before the project is considered complete?
Agree on how you will confirm the work is complete before signing. “The new site is live” is not enough: the agreed content must be present, critical journeys must work, and outstanding problems must have an owner and resolution plan. Name who handles quality assurance in the staging environment and who repeats critical checks after launch.
Concise launch checklist
- Before launch: Confirm the content inventory, approvals, backups, access, and rollback plan. Record baseline traffic and conversions for later comparison.
- Content and navigation: Check migrated pages, files, images, mobile layouts, menus, and links against the agreed inventory. Include agreed accessibility checks, such as keyboard navigation and form labels.
- Search readiness: Test changed URLs and 301 redirects, HTTP status codes, canonical tags, robots.txt, indexing controls, metadata, structured data, and the XML sitemap. Avoid sending unrelated removed pages to the homepage.
- Business journeys: Submit forms and confirm receipt. Test booking, phone links, checkout, and account access wherever they are in scope. For an online store, include payment gateway tests covering successful and failed transactions.
- Measurement: Check Google Analytics 4 events, conversion tracking, and consent behavior against the agreed measurement requirements.
- Live deployment: Verify DNS, the SSL certificate, HTTPS, and critical workflows on the live website. Repeat staging tests that depend on live configuration and check for loading or layout regressions. Agree how Core Web Vitals will be monitored after launch.
- Handover: Deliver account access, documentation, test results, and the outstanding-issues list. Confirm the monitoring period and support owner.
If Webflow is your destination, include Webflow SEO planning in the migration scope rather than leaving search requirements until after launch.
Separate completion testing from longer-term performance observation. A launch can pass functional tests while search engines are still processing changes. Schedule post-launch checks of Google Search Console, organic traffic to key landing pages, and lead delivery, but do not make unchanged rankings a guaranteed condition of completion.
Pay for a defined scope, not a vague promise
A properly scoped migration quote explains what moves, what gets rebuilt, what costs extra, and how completion will be demonstrated. Those details make prices comparable and give both sides a clear definition of done.
WFpulse specializes in Webflow development, combining technical execution with a focus on leads, bookings, and sales. Ongoing Webflow support and maintenance can be scoped separately to keep the site evolving after the move.
For a Webflow migration discussion with WFpulse, bring your current website, intended destination, must-keep features, and any proposed design or content changes. Start with those requirements before deciding whether a transfer, rebuild, or broader redesign is the right project.