Migrating to a new hosting provider raises many questions. This FAQ addresses the most common concerns about migrating to Data Mammoth, covering process, downtime, costs, and technical details.
General Questions
How long does a migration take?
The total migration process typically takes 3 to 5 business days from request to completion:
- Assessment and planning: 1 to 2 days
- Data transfer: Hours to 1 day (depends on data volume)
- Testing and verification: Same day as transfer
- DNS cutover: Minutes (propagation: hours)
Will my website go down during migration?
We aim to minimize downtime. During the migration itself, your current server continues running normally. Brief downtime (typically 15 to 60 minutes) may occur during the final cutover when we perform the last data sync and you switch DNS records.
Some visitors may experience intermittent issues during DNS propagation (up to a few hours), but this can be mitigated by lowering your DNS TTL before migration.
Can I migrate multiple servers at once?
Yes. We can migrate multiple servers simultaneously or sequentially. Discuss your requirements when submitting the migration request, and our team will create a plan that accommodates all your servers.
Do I need to cancel my current hosting first?
No. Keep your current hosting active during and after the migration until you have verified everything works correctly on Data Mammoth. Cancel the old hosting only after you are confident the migration is complete and successful. We recommend keeping the old server for at least a week after cutover.
Cost Questions
Is migration free?
Migration services may be complimentary for new customers, depending on the complexity and current promotions. Standard and complex migrations may have a fee. Contact our sales team or submit a migration request for specific pricing.
Are there hidden costs?
No. The migration cost (if any) is communicated upfront during the assessment phase. You will know the exact cost before work begins. The only ongoing cost is your Data Mammoth server plan.
Do I need to buy a new server for migration?
Yes. You need an active Data Mammoth server as the migration target. Choose a plan that meets or exceeds your current server's specifications.
Technical Questions
Will my IP address change?
Yes. Your new Data Mammoth server will have a different IP address. You will need to update your DNS records to point to the new IP. See Server Networking — IPs, DNS, Reverse DNS.
Will my data be transferred securely?
Yes. Data is transferred over encrypted connections (SSH/SCP/SFTP). Your data is never transmitted in plain text or through unsecured channels.
Can I keep my current operating system?
In most cases, yes. We will install the same OS version on your new Data Mammoth server. If you are using a very old or unsupported OS version, we may recommend upgrading to a supported version during migration.
What about my SSL certificates?
SSL certificates can be handled in several ways:
- Transfer existing certificates — We copy your current certificate files to the new server.
- Re-issue with Let's Encrypt — Free SSL certificates can be issued for your domains on the new server.
- Commercial certificates — Re-key or re-issue certificates with your SSL provider.
What about email?
If your current server handles email, we can migrate email accounts and messages. After migration, you will need to update your MX records to point to the new server. See Email Not Sending from Server for troubleshooting.
Can I migrate a server with Docker containers?
Yes. We can migrate Docker configurations, images, volumes, and compose files. The containers will be recreated on the new server with the same configuration.
What about databases?
Databases (MySQL, PostgreSQL, MongoDB, etc.) are exported from the current server and imported to the new one. We verify data integrity after import.
Process Questions
Can I perform the migration myself?
Absolutely. Our Server Migration Checklist provides a comprehensive step-by-step guide for self-service migration. Our support team is available if you need help during the process.
What access do you need to my current server?
For assisted migration, we typically need:
- SSH access (root or sudo user).
- Database admin credentials.
- Control panel access (if applicable).
Can I roll back if something goes wrong?
Yes. Your current server is not modified during migration. If anything goes wrong on the new server, simply revert your DNS records to point back to the original server. That is why we recommend keeping the old server active until migration is fully verified.
How do I know migration is complete?
Our team will notify you when all data has been transferred and tested. We provide a verification checklist and ask you to confirm that everything works correctly before the final DNS cutover.
What happens to my old server after migration?
Your old server remains under your control with your previous hosting provider. We recommend:
What to Do Next
- How to Request a Server Migration — Start your migration.
- Server Migration Checklist — Prepare for the move.
- Server Migration Overview — Full service details.
- How to Submit a Support Ticket — Ask additional questions.