Self-service
Make yourself at home.
Follow the guide. Test your preview. Move your domain when you’re ready.
Next.js migration guideMove to Adios
A new home.
For your next big thing.
Your apps, data, and deployments. A clear path from your current host to Adios.
Coming fromVercelRailwayAWSYour stack
Your move, in three stepsWalkthrough
Bring your stack.
Map your apps, data, and dependencies. Choose what moves first.
Apps & APIs Databases Files & storage Release pipelines
Your move. Your way.
Take the lead.
Or bring our team.
With Adios engineers
Let’s move it together.
A scoped migration for your applications, databases, and release pipelines.
Talk about your stackThe whole application
More than a Git import.
A repository is the starting point. A working production environment is the destination.
Applications & background work
Inventory web apps, APIs, workers, and scheduled jobs. Check runtime versions, build commands, native dependencies, and health checks before choosing the deployment shape.
Deliverable: a service and dependency mapDatabases & persistent files
Plan exports, backups, transfer time, and validation. Decide how to handle writes during the move and which databases or storage services should stay external.
Deliverable: a data transfer and recovery planSecrets, domains & integrations
Recreate environment configuration securely. Review DNS, certificates, login callbacks, webhooks, email, payments, and network access so the application works beyond its homepage.
Deliverable: a configuration and connectivity checklistDeployments & team handoff
Rebuild the path from repository to production. Agree on release checks, access permissions, rollback steps, and who owns the environment after the move.
Deliverable: a tested release workflow and runbookYour starting point matters.
Portability depends on the services you use, not just where your code lives. Here is what we look at first.
Vercel & framework hosting
Start with the application runtime, then review provider-specific functions, edge behavior, image handling, and hosted add-ons. A successful build is the first check; authentication, uploads, and background work need their own tests.
Railway, other PaaS & VPS hosting
Map each process, attached volume, database, and scheduled task. Carry over start commands and health checks, then verify service-to-service connections and persistent paths in the new environment.
AWS & larger cloud environments
Separate portable application services from provider-managed dependencies. Review identity, private networking, queues, storage APIs, and data transfer constraints. Move in phases; keep services external where that is the better fit.
From first call to first release
A plan you can follow.
Use these checkpoints for a self-service move. For an assisted migration, we turn them into agreed deliverables for your stack.
Map the move
Review your architecture, traffic, data volume, and constraints. Agree on what moves, what stays, and who is responsible for each task.
You leave with: scope, dependencies, and acceptance criteria
Rehearse in a preview
Deploy a representative environment and test critical journeys: sign-in, payments, uploads, jobs, and database access. Validate transferred data and measure performance against your needs.
You leave with: test results and a go-live checklist
Switch with a fallback
Confirm backups, data synchronization or a write pause, DNS changes, and the maintenance window. Define rollback triggers and how new writes will be reconciled if traffic returns to the old system.
You leave with: a cutover plan and named decision-makers
Settle into production
Check traffic, errors, and data after the switch. Hand over access, release instructions, and recovery procedures. Retire old resources only after the agreed validation and retention period.
You leave with: an operating runbook and clear ownership
Bring the shape of your stack.
For the first conversation: your framework and hosting setup, connected services, approximate data size and traffic, and any deadline or downtime constraints. We use that to define the assessment and a tailored migration quote.
Before you pack
A few things
worth knowing.
Can I move one application first?
Yes. Start with one app, test its dependencies, and move the rest when you’re ready. Existing external services can stay where they are if connectivity and security meet your needs.
Will my migration have downtime?
We agree on the cutover, maintenance window, and rollback plan before the move. Downtime depends on your app and data; zero downtime is not guaranteed.
What happens to my data?
Databases, files, and users need a separate transfer plan. Importing source code does not move them automatically. Backups and data checks are part of the migration scope.
Can your engineers handle the move?
Yes, through a separately scoped migration project. We assess your setup, agree on deliverables, and provide a tailored quote before work begins.
Ready when you are