Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Migrate from AWS

Move an AWS workload to DotMoose

Identify the AWS services your application uses, including storage, databases and identity. Check replacements and transfer costs before committing to a move.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

What needs to move

Check moving from AWS by identifying which pieces are ordinary compute and which depend on managed AWS services, IAM, VPC networking, load balancers, object storage, databases, queues, DNS, or secrets that need an explicit replacement.

02

Test the destination

Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.

03

Copy the final changes

Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.

04

Switch traffic and retain rollback

Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.

Field guide

Sorting AWS compute from managed services

An AWS account mixes ordinary servers with managed services that have no direct equivalent elsewhere. List the EC2 instances and their storage, then list everything around them: RDS databases, S3 buckets, load balancers, Route 53 zones, IAM roles and stored secrets. Servers export as files and dumps, while each managed service needs an export tool and a named replacement.

Permissions cause the hidden failures. Applications often read files or databases using an IAM role attached to the old server, and that access vanishes at the destination until new credentials exist. Inventory every role, key and secret the workload uses, issue destination credentials during the rebuild, and test each integration, including mail sending and storage access, before DNS moves.

01

Service dependency map

Draw which AWS services the application calls at runtime. Queues, email services and serverless functions each need a replacement decision.

02

Route 53 export

Export the full Route 53 zone, including health check related records and mail records. DNS often outlives the server move and should move on its own schedule.

03

Egress and allowlists

Note the old server addresses that partners and APIs allowlist. Share the new address early so external access survives cutover day.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Move an AWS workload to DotMoose: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move