Migrate your FiveM server to HebergTonServ

Migrating a FiveM server may seem complex, but by following this step-by-step guide, you’ll transfer your server safely while optimizing transfer time through data compression.

🎯 Why migrate to HebergTonServ?

• ✅ Optimal performance: Latest generation hardware
• ✅ Anti-DDoS protection: Maximum security included
• ✅ Responsive support: 24/7 technical team available
• ✅ Competitive pricing: Unbeatable value for money
• ✅ Intuitive panel: Simplified server management

📋 Prerequisites before migration

Before starting, make sure you have:

• ✅ Full access to your old server (FTP/SFTP)
• ✅ MySQL database backup (SQL export)
• ✅ HebergTonServ account created and server ordered
• ✅ FTP client installed (FileZilla, WinSCP, or Cyberduck)
• ✅ Compression software (7-Zip, WinRAR, or tar on Linux)
• ✅ Sufficient disk space on your PC for temporary files

⚠️ IMPORTANT: Don’t delete ANYTHING on your old server until you’ve verified everything works on HebergTonServ!

🗂️ Step 1: Inventory your files

1.1 Identify critical files

Connect to your old server and identify:

📁 Your FiveM server/
├── 📁 resources/          ← Scripts and resources (ESSENTIAL)
│   ├── 📁 [esx]/
│   ├── 📁 [qb-core]/
│   ├── 📁 [custom]/
│   └── 📁 [mapping]/
├── 📁 server-data/        ← Configuration files
│   └── 📄 server.cfg      ← Server configuration (CRITICAL)
├── 📁 cache/              ← TO DELETE (can be regenerated)
│   ├── 📁 files/
│   ├── 📁 http-cache/
│   └── 📁 priv/
├── 📄 server.cfg          ← Sometimes at root
├── 📄 txData/             ← cfx.re data (KEEP)
└── 📁 logs/               ← Logs (optional, often large)

1.2 Estimate total size

# On Linux (SSH)
du -sh /path/to/server/*

# Example result:
# 2.4G    resources
# 850M    cache          ← TO DELETE before compression
# 120M    server-data
# 45M     txData
# 1.2G    logs           ← Optional

🧹 Step 2: Cleanup and optimization (CRUCIAL)

2.1 Delete cache (huge time saver!)

The cache/ folder can reach several GB and significantly slow down transfer. It will be automatically recreated by FiveM on startup.

Via FTP (FileZilla/WinSCP)

1. Navigate to your server root folder
2. Right-click on cache/ folder → Delete
3. Confirm deletion

Via SSH (Linux)

# Go to server root
cd /path/to/your/server

# Delete cache
rm -rf cache/

# Verify deletion
ls -la | grep cache
# (should return nothing)

💡 Time saving: Deleting an 800 MB cache can reduce transfer time by 15-30 minutes!

2.2 Clean old logs (optional)

If your logs are large and non-critical:

# On Linux
cd logs/
rm -f *.log.1 *.log.2 *.log.old

# Keep only recent logs
find . -name "*.log" -mtime +7 -delete

2.3 Remove temporary files

# Common temporary files
rm -rf *.tmp
rm -rf *.temp
rm -rf .DS_Store
rm -rf Thumbs.db

📦 Step 3: Data compression

Compression significantly reduces transfer time (50-70% size reduction).

3.1 Compression on Windows

With 7-Zip (recommended - free)

1. Download 7-Zip: https://www.7-zip.org/
2. Transfer all files to your PC via FTP
3. Right-click on server folder → 7-Zip → Add to archive
4. Recommended configuration:

   Archive format: .7z
   Compression level: Ultra
   Compression method: LZMA2
   Dictionary size: 64 MB
   Word size: 64

5. Name the archive: fivem-server-backup.7z
6. Click OK (may take 5-15 minutes depending on size)

Expected result:

Original size: 2.5 GB
Compressed size: 850 MB (66% reduction)

With WinRAR

1. Right-click → Add to archive
2. Format: RAR
3. Compression method: Best
4. Create solid archive: Checked

3.2 Compression on Linux/macOS (SSH)

With tar + gzip (fast)

# Go to parent directory
cd /path/to/parent/

# Compress with gzip (fast, medium compression)
tar -czf fivem-server-backup.tar.gz server-folder-name/

# Check size
ls -lh fivem-server-backup.tar.gz

With tar + xz (maximum compression)

# Maximum compression (slower but better ratio)
tar -cJf fivem-server-backup.tar.xz server-folder-name/

# Show progress
tar -cJvf fivem-server-backup.tar.xz server-folder-name/

With zip (Windows compatible)

zip -r -9 fivem-server-backup.zip server-folder-name/

⏱️ Time comparison:

• Without compression: 2.5 GB = ~40 min transfer (100 Mbps)
• With compression: 850 MB = ~13 min transfer (same speed)
• Saved: 27 minutes!

🚀 Step 4: Transfer to HebergTonServ

4.1 Connect to HebergTonServ panel

1. Go to: https://manage.hebergtonserv.com
2. Login with your credentials
3. Select your FiveM server from the list

4.2 Stop the server

IMPORTANT: Stop the server before transferring files!

1. In panel → Console tab
2. Click Stop (red button)
3. Wait for message: Server stopped

4.3 SFTP Access

Get SFTP credentials

1. In the panel, go to the Settings tab
2. Click on SFTP Details (or “Détails SFTP”)
3. A window will open with your connection credentials:

   Host: sftp.hebergtonserv.com
   Port: 2022
   Username: hts_XXXXX (your unique identifier)
   Password: [your panel password]

💡 Important: SFTP credentials are only available through the “SFTP Details” button in the Settings tab of the panel. Don’t try to guess the host or port, use the exact information provided.

Connection with FileZilla

1. Open FileZilla
2. Site Manager (Ctrl+S)
3. New Site:

   Protocol: SFTP
   Host: sftp.hebergtonserv.com
   Port: 2022
   Logon Type: Normal
   User: hts_XXXXX
   Password: [your password]

4. Click Connect

4.4 Transfer compressed archive

Method 1: Upload archive (RECOMMENDED)

1. In FileZilla, navigate to your server root
2. Drag and drop your .7z or .tar.gz archive
3. Wait for transfer completion (progress bar at bottom)

📊 Transfer time example:
850 MB with 100 Mbps connection = ~13 minutes
850 MB with 50 Mbps connection = ~25 minutes

Method 2: Direct transfer (without local compression)

If you compress directly on old server:

1. Download archive from old server → your PC
2. Upload archive to HebergTonServ

📂 Step 5: Extraction on HebergTonServ

5.1 Access file manager

Panel → Files tab

5.2 Extraction via panel

1. Right-click on archive → Extract
2. Choose destination folder: /
3. Wait for extraction completion

5.3 Extraction via SSH (alternative)

If you have SSH access:

# For .tar.gz
tar -xzf fivem-server-backup.tar.gz

# For .tar.xz
tar -xJf fivem-server-backup.tar.xz

# For .zip
unzip fivem-server-backup.zip

# For .7z (install p7zip first)
7z x fivem-server-backup.7z

5.4 Verify extraction

# List files
ls -la

# Check resources
ls -la resources/

# Check server.cfg
cat server.cfg

✅ Step 6: Post-migration verification

Complete checklist

• Server starts without errors
• Database works (player connection test)
• Resources load (all in logs)
• Jobs work (ESX/QBCore test)
• Vehicles spawn (garage test)
• Inventories are correct
• Blips/markers display
• Chat works
• Admin commands respond
• No abnormal lag

Recommended tests

# Test 1: Simple connection
1. Connect to server
2. Verify character loads

# Test 2: Interactions
1. Open menu (F6, F5, etc.)
2. Use ATM
3. Open inventory

# Test 3: Performance
1. F8 → resmon
2. Check RAM and CPU

🚨 Common issues troubleshooting

Issue 1: Missing resources

Symptom: Failed to load resource [name]

Solution:

# Verify folder exists
ls -la resources/[name]/

# Check permissions
chmod -R 755 resources/[name]/

# Check fxmanifest.lua
cat resources/[name]/fxmanifest.lua

Issue 2: MySQL error

Symptom: Failed to connect to MySQL

Solutions:

1. Verify mysql_connection_string
2. Test connection in phpMyAdmin
3. Verify database contains tables:

   SHOW TABLES;

Issue 3: Invalid license

Symptom: Invalid license key

Solution:

1. Check on https://keymaster.fivem.net/
2. Copy exact key (no spaces)
3. Update in server.cfg
4. Restart server

Issue 4: Invisible server

Symptom: Server not found in list

Solutions:

1. Verify port is open
2. Check sv_master1 in server.cfg:

   sv_master1 ""

3. Wait 5-10 minutes (synchronization delay)

Issue 5: Corrupted cache (after migration)

Symptom: Missing textures, random crashes

Client-side solution:

%localappdata%\FiveM\FiveM Application Data\cache
→ Delete cache folder

Server-side solution:

# Stop server
# Delete new cache
rm -rf cache/
# Restart

🔗 Useful resources

• HebergTonServ Panel: https://manage.hebergtonserv.com
• FiveM Documentation: https://docs.fivem.net/
• Support Discord: https://discord.gg/26xerySCfX
• SQL Tutorial: MySQL FiveM Connection
• Community Forum: https://forum.cfx.re/

✨ Conclusion

Congratulations! Your FiveM server is now hosted on HebergTonServ with:

• ✅ Successful migration without data loss
• ✅ Optimized performance thanks to our infrastructure
• ✅ Enhanced security with included Anti-DDoS
• ✅ Available support 24/7 via Discord

Recommended next steps

1. Join our Discord for community advice
2. Test panel features (web console, SFTP, databases)

🆘 Need help?

If you encounter difficulties during migration:

1. Check logs in console (Panel → Console)
2. Contact support:
   • Discord: https://discord.gg/26xerySCfX

Our technical team is here to assist you free of charge with your migration! 🚀

Total estimated migration time: 45-90 minutes (depending on server size) Difficulty: Intermediate Bandwidth savings: 50-70% thanks to compression