Requesting a server migration is the first step toward moving your infrastructure to Data Mammoth. This guide explains what information to provide, how to submit your request, and what happens after you submit.
Before Requesting
Gather the following information about your current server to help our team plan the migration efficiently:
Server Details
- Current server IP address — The IP of the server being migrated.
- Operating system and version — e.g., Ubuntu 22.04, CentOS 9, Debian 12.
- Control panel — Whether you use a server management panel (note the type).
- Total disk usage — How much data needs to be transferred (run
df -h).
Services Running
- Web server — Apache, Nginx, or other.
- Database — MySQL, MariaDB, PostgreSQL, MongoDB, etc.
- Programming languages — PHP version, Python, Node.js, Ruby, etc.
- Email — Whether the server handles email services.
- Other services — Any additional services (Redis, Memcached, Docker containers, etc.).
Websites and Applications
- Number of websites — How many websites or applications are hosted.
- Domain names — List of domains hosted on the server.
- CMS — WordPress, Joomla, Drupal, custom application, etc.
- Database count and sizes — Number and approximate size of databases.
Access Credentials
Our team will need access to your current server to perform the migration:
- SSH access — Root or sudo user credentials or SSH key.
- Database access — Database admin credentials (if needed separately).
- Control panel access — Login credentials for the management panel (if applicable).
Submitting the Request
Step 1 — Order a Data Mammoth Server
If you have not already, order a Data Mammoth server that matches or exceeds your current server's specifications:
See How to Order Your First Server.
Step 2 — Submit a Migration Ticket
text
Current Server Details:
- IP: [current server IP]
- OS: [operating system and version]
- Disk usage: [total GB used]
- Control panel: [if any]
Services:
- Web server: [Apache/Nginx/other]
- Database: [MySQL/PostgreSQL/other]
- PHP version: [if applicable]
- Other services: [list any]
Websites/Applications:
- Number of sites: [count]
- Domains: [list domains]
- CMS: [WordPress/custom/etc.]
- Database count: [number]
Target Data Mammoth Server:
- Server name/IP: [new server details]
Preferred Migration Schedule:
- Date/time: [when you want the migration to happen]
- Timezone: [your timezone]
- Acceptable downtime window: [e.g., 2-4 AM UTC]
Access to Current Server:
SSH: [how you will provide access]
Step 3 — Provide Access
After submitting the ticket, our migration team will respond with:
- Confirmation that the request is received.
- Any additional information needed.
- Instructions for securely sharing access credentials.
What Happens After Submission
Assessment Phase (1-2 Business Days)
Our team reviews your request and:
- Evaluates the complexity of the migration.
- Creates a migration plan.
- Identifies any potential issues or special requirements.
- Provides a timeline and confirms the migration schedule.
Preparation Phase
- We prepare the target Data Mammoth server with the necessary software stack.
- We test connectivity to your current server.
- We confirm the migration plan with you.
Migration Phase
- Data is transferred from your current server to the new one.
- Configurations are replicated.
- Databases are exported and imported.
- Services are configured and tested on the new server.
Verification Phase
- All websites and applications are tested on the new server.
- We provide you with a temporary URL or direct IP access to verify everything works.
- You confirm that the migration is correct.
DNS Cutover
- You update your DNS records to point to the new Data Mammoth server's IP.
- DNS propagation occurs (typically a few hours).
- We monitor for any issues during the transition.
Migration Timeline
| Phase | Duration |
|---|---|
| Assessment | 1 to 2 business days |
| Preparation | 1 to 2 business days |
| Data transfer | Hours to 1 day (depends on data size) |
| Verification | Same day as transfer |
| DNS cutover | Minutes (propagation: hours) |
What to Do Next
- Server Migration Checklist — Prepare for your migration.
- Server Migration FAQ — Common questions answered.
- Server Networking — IPs, DNS, Reverse DNS — DNS configuration for cutover.
- Server Migration Overview — Full migration service details.