Move it to us. We do the lift.
Whatever it runs on now, we move it — one fixed monthly rate, a rehearsed cutover with little-to-no downtime, and once it's here CodeHerder keeps it shipping.
If it runs on a server, we move it
Not just static sites and not just what we sell out of the box — any app, any stack, moved as one unit.
Static sites & SPAs
Anything already built — React, Vue, plain HTML — moved to the edge network with no rebuild required.
Node, Python, Ruby, Go, PHP, Java
Whatever your app is written in, it runs on a dedicated instance sized to the workload.
Postgres, MySQL, Redis
The database moves with the app — provisioned, backed up nightly, and restored alongside it.
Docker & containers
Already containerised? We run the images you have rather than asking you to re-package anything.
Cron jobs & background workers
Scheduled jobs and queues that never see a browser still need somewhere to live — they move too. See Background jobs for how one actually runs here.
Files & object storage
Uploads, exports, backups — copied across and served from durable storage on the other side. See Files for what survives the move.
WordPress & CMS platforms
Database, uploads, and plugins moved as one unit, not reassembled by hand.
How the move works
Five steps from "point us at it" to a live migration you don't have to think about again.
- 01
Point us at it
Read access to the repo, or to the current host — that’s the whole ask. No discovery questionnaire before we can start looking.
- 02
We stand up a copy
The stack is provisioned as code on our side: a staging mirror you can click through and check before anything is live.
- 03
Rehearsed cutover
DNS and TLS switch over on a schedule you set, with little-to-no downtime and a rollback ready if anything looks wrong.
- 04
We run it
Monitoring, security patching, and nightly backups start from day one — the same managed posture as anything else we host.
- 05
Keep shipping
It’s hosted here and defined as code now, so CodeHerder’s agents can iterate on it directly: brief a change, an agent opens a pull request, the same pipeline ships the merge.
No surprise invoice for the move itself
The migration is the on-ramp, not a separate product — priced and timed the same honest way as everything else here.
Standard moves
Typically part of onboarding — no separate migration invoice for a stack that fits the common shapes above.
Anything complex
Unusual stacks or extra-large data sets get a flat quote up front, before any work starts — never a bill after the fact.
How long it takes
Most stacks are live within days of getting access, not weeks of back-and-forth.
Leaving is just as easy
An on-ramp is only trustworthy if the off-ramp is just as real.
Migration questions
The questions this page raises on its own. General hosting questions live on the homepage.
01Will my site go down during the move?
The cutover is rehearsed against a staging copy first, and DNS/TLS switch over on a schedule you set — most moves see little-to-no visible downtime. A rollback is ready if anything looks wrong.
02Which stacks can you move?
Static sites, SPAs, apps in most common languages, relational and key-value databases, containers, background workers, and CMS platforms. If it runs on a server, we can move it — talk to us about anything unusual.
03Do you charge for migration?
Standard moves are typically folded into onboarding at no separate line item. Anything unusually complex gets a flat quote up front, so there’s never a surprise invoice for the move itself.
04What do you need from me?
Read access to your repo and to your current host is usually enough to get started. We’ll ask for anything else specific to your stack once we’ve had a look.
05Can you modernise it while moving it?
Yes — if the move is a good moment to pay down technical debt or rebuild a piece properly, CustomLabs can do that work alongside the cutover instead of just lifting it as-is.
06How do we keep changing it afterwards?
Once it’s hosted here and defined as code, CodeHerder’s agents can iterate on it directly — brief a change in plain language, an agent opens a pull request, and the same pipeline ships the merge.
07Am I locked in?
No. Everything is defined as code, so export or a documented handover is free, any time — the same portability we offer on every other stack we host.
08Will my old URLs keep working, and will I lose search rankings?
Only if a redirect map is set up before the old addresses go dark — that's a briefed change, not something that happens on its own. Done right, with a permanent redirect from each old address to its new one, search rankings carry over instead of resetting. See Delivery for the full rule set.
Keep exploring
- What we host
Moving a specific stack in? See the register and its own deep page, if it has one.
- Platform
How the edge network, storage, and dedicated compute fit together.
- Dedicated compute
A fixed-price instance for APIs, databases, and full applications.
- Pricing
The full rate card — flat, predictable, and posted in the open.
- The Loop
What happens after the move: brief a change, an agent opens a PR, the pipeline ships it.
- Domains
The DNS/TLS cutover above, followed in full — the record sheet, the propagation window, and the rollback.
- Environments
The staging mirror above, specified — its address, who can reach it, and how it differs from the standing environment an add-on sells.
- Background jobs
The "cron jobs & background workers" row above, worked in full — where each one runs once it moves, and how the clock is wired.
- Guide: static or dedicated?
Not sure what you’re moving to? A decision guide to the question underneath the question.
- For: no dev team
Moving in because the site's original developer moved on? Start here.
- Onboarding
The move above is Day 2–3 of a bigger first week — see the whole thing, hour by hour.
- Portability
The no-lock-in promise on this page, spelled out: the pack manifest, the procedure, and what stops when you go.
- Delivery
The redirect map behind the "old URLs" FAQ above, in full — every URL rule, the cache, and the response headers.
Ready to move?
Tell us what you're running and where it lives now — one fixed monthly rate, within a business day.