Founding customer pilot now open in Addis Ababa·Prices in ETB, same at renewal·Join the pilot →
✧ MIGRATION

Move an application from another platform.

Whether it runs on Render, Vercel, Netlify, Heroku, a shared cPanel account or a server you manage yourself, the move follows the same path.

A developer working with code on two screensInventoryPreviewCutover
WHAT MAPS ACROSS

Your current setup, translated

✓
Build and start commands

They come with you. A project records how it is built and which branch goes to production.

✓
Environment variables

Moved once into your account, encrypted, with production-only values kept out of preview builds.

✓
Preview deployments

Branches other than production build as previews, so code review keeps working the way it does now.

✓
Custom domains and TLS

Prove the name with a DNS record, then point it here. Certificates are issued and renewed for you.

✓
Background jobs

Long-running work runs beside the application and picks up where it stopped.

✓
Databases and object storage

Plan these first. Size, export method and restore time decide the shape of the whole move.

THE SIX STEPS

A cutover that surprises nobody

✓
1 · Inventory

Every service, domain, variable, scheduled job, data store and third-party callback. The forgotten webhook is the usual cause of a bad migration.

✓
2 · Connect the repository

Create the project, set the production branch, and record the build command you already use.

✓
3 · Build a preview

Deploy a branch first and exercise the real paths: sign-in, uploads, payments callbacks, scheduled work.

✓
4 · Move the data

Export, import, then compare counts. Plan a short second sync at cutover for anything still being written.

✓
5 · Point DNS

Lower the TTL a day ahead, prove the name, then switch. Keep the old platform serving until the new one is proven.

✓
6 · Verify, then decommission

Check logs, invoices and background work for a full billing cycle before you turn anything off.

BEFORE YOU MOVE

Five questions worth answering first

How long does a migration take?+

A small application with no data store can be moved in an afternoon. The data is what sets the schedule: export time, import time and the length of the second sync at cutover.

Can I keep my domain where it is registered?+

Yes. Ownership is proven with a TXT record at your current DNS provider, and the registration stays exactly where it is.

Will my build work without changes?+

If it builds today with a documented command and configuration that comes from environment variables, it builds here. Anything that depends on files written into the running server needs a plan first.

What happens to the platform I am leaving?+

Keep it running. DNS is reversible while the old service still answers, which is what makes a cutover safe.

Who does the work?+

You can run the whole move from your own account. If you would rather plan it with someone, describe the system and the team will work through the steps with you.

NEXT STEP

Plan the move

Send us the inventory, not the whole system.

A list of services, domains, variables and data stores is enough to plan a cutover window and tell you what to watch.

Plan a migrationHow your system runs here

Platform names on this page describe where a workload is moving from. They are the trademarks of their owners, and no affiliation, endorsement or partnership is implied.

LET’S BUILD WHAT’S NEXT

Ready to explore HuluBuild Cloud?

Talk through a website, application or agency use case before choosing a plan.