Pricing and quotation guide
Website content migration cost
Content migration costs depend on how much content there is, how varied it is and how easily it comes out of the old platform. A few dozen simple pages move quickly; thousands of posts with custom fields and page-builder layouts take far longer.
This page explains each cost factor and how to reduce the volume before you pay to move it.
Illustrative diagram
Content migration cost
- Volume
- Pages
- Posts
- Media
- Variety
- Types
- Fields
- Difficulty
- Export method
- Clean-up
- Builders
- Shortcodes
Volume, variety and difficulty
Three things decide most of the cost. Volume is how many items need moving. Variety is how many content types and custom fields they have. Difficulty is how hard the old platform makes it to get content out: a clean export is quick, while extracting from an unusual system can take real investigation.
Clean-up comes on top. Content written in a plain editor needs little; content built with page builders or full of embedded widgets needs much more.
Cost drivers
- Volume
- More pages, posts and media mean more to move and verify.
- Content types and fields
- Each type needs mapping and testing.
- Export difficulty
- Unusual or closed platforms need extra extraction work.
- Formatting clean-up
- Page-builder layouts and shortcodes need rework.
- Media
- Moving and relinking large image and document libraries.
- Redirects
- Every changed address needs a destination.
Costs paid to third parties (separate from our fees)
- Migration tools or plugins, if used
- New platform subscription
- Keeping the old hosting until verification is complete
These are paid to their providers and listed where they apply.
Reduce volume before migrating
| Content | Typical decision |
|---|---|
| Outdated news and event posts | Retire with redirects to a relevant section |
| Duplicate or near-duplicate pages | Merge into one |
| Thin pages with no visitors | Retire or fold into stronger pages |
| Evergreen guides and service pages | Migrate and improve |
Automated versus manual
Automated migration through exports or APIs is efficient for large volumes of consistently structured content. Manual migration is often better for a small number of important, heavily designed pages that need rebuilding anyway. Most projects combine both: automate the bulk, hand-build the key pages.
Information for an accurate estimate
Counts
- Pages, posts and other content types
- Approximate media library size
Context
- Old and new platforms
- Whether a page builder was used
- Content you already know can be retired
Costs after migration
Once content is on the new platform, ongoing costs depend on that platform: subscriptions, maintenance and editing time. A migration that leaves content clean and structured makes future editing quicker, which is part of the value of the clean-up work.
Why clean-up costs vary
Two sites with the same number of pages can need very different clean-up. Content written in a simple editor usually needs little more than checking. Content built with a page builder, shortcodes or embedded widgets has to be rebuilt in the new platform's structure, page by page or with careful automation.
Grading a sample of pages before quoting shows which situation applies and keeps the estimate honest.
Pruning before migrating
Illustrative example — not a client case study
Situation: A site has around 900 posts collected over many years, most of them short news items.
- An inventory shows a small number of guides and service pages receive most visits.
- Old news items are retired with redirects to a news archive page.
- The remaining content is migrated and cleaned.
What this shows: The migration moves a fraction of the original volume and the new site is easier to navigate. This example is illustrative.
A test batch keeps estimates honest
Migrating a small sample of each content type first shows how much clean-up is really needed. If the sample reveals more work than expected, the estimate can be adjusted before the bulk migration begins, rather than discovered halfway through.
Questions about website content migration cost
Is content migration priced per page?
We estimate from volume, variety, export difficulty and clean-up needs rather than a flat per-page rate.
Does a page builder increase cost?
Usually, because builder layouts do not transfer and need rebuilding.
Can pruning really save much?
Often yes. Old news, duplicates and thin pages can make up a large share of a site.
Is media migration included?
Yes, with links updated. Very large libraries may need more time.
Do redirects cost extra?
They are part of the migration, scaled to the number of changed addresses.
What if the old platform is hard to export from?
Extraction may need extra investigation, which is estimated separately once we know the platform.
Is a test migration charged?
A small test batch is part of the work. It reduces risk and often saves time overall.
Can we migrate in stages to spread cost?
Yes. Key pages first, archives later, with redirects added as content moves.
Can you migrate from a site builder?
Usually, though builders often have limited exports, which can mean more manual work.
Is verification charged separately?
Verification is part of every migration and listed so you can see the effort involved.
Does moving to a hosted platform change the cost?
Hosted platforms often have structured imports that speed up migration, but their content models may need more mapping decisions.
Request a Custom Quote
Ask about Website content migration cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.