Migrations that keep what you've earned.
MapleGrowth moves websites off legacy systems and page builders onto WordPress, PHP, or a headless CMS, with content, URLs, and search rankings carried over on an explicit redirect map. Projects are quoted before work starts, and we maintain the new site after the move.
What counts as a migration here?
Three moves make up most of this work. A legacy system, an aging CMS or a custom build nobody maintains, rebuilt on WordPress or PHP. A page-builder site converted to a headless CMS once the builder has become the bottleneck. And a WordPress site that has outgrown its theme and plugin stack, rebuilt clean on the same platform.
The part that decides whether a migration succeeds is invisible: the redirect map. Every URL that ranks or has earned links gets an explicit destination before anything switches over, because rankings lost in a careless migration take months to rebuild.
What's included
- A migration audit: what exists, what moves, what should retire
- A full redirect map, written before anything switches over
- The rebuild, on WordPress, PHP, or a headless CMS
- Content, media, and integration carry-over, checked page by page
- A care plan after launch: updates, patches, backups, uptime checks
Four phases, one throughline.
Discover
A full inventory of the current site: pages, rankings, integrations, and the parts nobody remembers exist.
Design
The target stack, the new structure, and the redirect map. You approve all three before a line is built.
Develop
The rebuild and the carry-over, with the old site untouched and live the whole time.
Deploy
A monitored cutover, then weeks of watching Search Console for anything the map missed. Maintenance starts here.
Where the proof stands
Our published build record is Voyamore and this site: both fast, both owned outright by their operators, both inspectable right now.
We have not published a named migration case study yet, and we won't invent one. What we can walk through on a call is the redirect-mapping process itself and the checklist a cutover runs on, in as much detail as you want.
Maintenance after the move is scoped in writing: what a month covers, what counts as extra, and what it costs. A care plan is a contract, never a surprise invoice.
Asked before signing.
Will we lose search rankings in the move?
The risk is real, which is why the redirect map is the first deliverable, not an afterthought. Every ranking URL gets an explicit destination, and we watch Search Console through the weeks after cutover. Nobody honest can promise zero movement; what we commit to is mapping, monitoring, and fixing fast.
How much does a migration cost?
Project work starts at $1,500, and the quote is fixed before anything begins. What moves the number: page count, how messy the source content is, integrations that must survive, and whether the design is being kept or replaced. The audit tells us; then you get one price.
Can we keep our current design?
If the design is worth keeping, yes: we rebuild the stack underneath it. Often the honest recommendation is a refresh at the same time, since the site is being rebuilt anyway. We will tell you which case yours is and why, and the call is yours.
What happens after launch?
A care plan, scoped in writing: platform and plugin updates, security patches, backups, and uptime checks on a monthly cadence. You are never locked in; the site, the code, and every account are yours, and the plan can end whenever you want it to.