Migrate from Odoo.sh
Move your existing Odoo.sh project to OEC.SH with zero data loss.
Before You Start
Make sure you have:
- Admin access to your Odoo.sh project
- A backup downloaded from Odoo.sh
- Your Git repository accessible
- An OEC.SH account with a server ready
Step 1: Download Backup from Odoo.sh
- Log in to Odoo.sh
- Go to your project → Backups
- Find your production backup
- Click Download → Choose Full backup
- Save the
.zipfile
Important: The backup contains your database dump and filestore.
Step 2: Upload Backup to Cloud Storage
OEC.SH needs your backup in cloud storage to restore it.
Option A: Cloudflare R2 (Recommended)
- Go to Settings → Storage Providers
- Click Add Storage → Cloudflare R2
- Enter your R2 credentials
- Upload your Odoo.sh backup to a bucket
Option B: AWS S3
- Add your S3 bucket as a storage provider
- Upload the backup file to your bucket
Option C: Other Providers
We support: MinIO, Backblaze B2, FTP, SFTP
Step 3: Create Migration Record
- Go to Migrations in the sidebar
- Click New Migration
- Fill in the details:
- Name: e.g., "Production from Odoo.sh"
- Storage Provider: Select where you uploaded the backup
- Backup File: Select or enter the backup path
- Database Name: The database name from Odoo.sh
- Click Create Migration
OEC.SH will verify the backup is accessible.
Step 4: Create Project & Environment
- Go to Projects → Create Project
- Connect your Git repository (same one from Odoo.sh)
- Select the correct Odoo version
- Click Create Project
Then create an environment:
- Click Add Environment
- Configure as production:
- Type: Production
- Resources: Match or exceed your Odoo.sh plan
- In the Migration section:
- Enable Restore from Migration
- Select your migration record
- Click Create Environment
Step 5: Deploy with Migration
- Open your new environment
- Click Deploy
- OEC.SH will automatically:
- Download your backup from cloud storage
- Restore the database
- Restore the filestore
- Configure Odoo
- Start the environment
This takes 5-15 minutes depending on backup size.
Step 6: Verify Everything Works
Once deployment completes:
- Click your environment URL
- Log in with your existing Odoo credentials
- Verify:
- All data is present
- Custom modules work
- Reports generate correctly
- File attachments load
Step 7: Update DNS (Go Live)
When you're ready to switch over:
- Go to Settings → Domain
- Add your custom domain
- Update DNS at your registrar:
- Point A record to your OEC.SH server IP
- Or use CNAME to your OEC.SH subdomain
- Wait for DNS propagation (5-30 minutes)
- SSL certificate auto-provisions
Migration Checklist
Before going live:
- All users can log in
- Emails are sending correctly
- Scheduled actions running
- Integrations working (payment providers, shipping, etc.)
- Backups configured on OEC.SH
- Team members invited with correct permissions
Common Issues
"Database already exists"
The migration was already restored. To re-restore:
- Go to environment Settings → Advanced
- Click Force Re-Restore
- Type
RESTOREto confirm - Redeploy
Warning: This overwrites all current data!
"Backup file not found"
Check that:
- Storage provider credentials are correct
- Backup file path is exact
- File permissions allow access
"Addon not found"
Your custom addons might be missing:
- Ensure all addons are in your Git repository
- Check
addons_pathincludes your addon directories - Verify addon dependencies are installed
Cost Comparison
| Odoo.sh Plan | OEC.SH Equivalent | Savings |
|---|---|---|
| One App ($24/mo) | Starter ($49/mo for unlimited) | More value |
| Standard ($48/mo) | Pro ($99/mo with replicas) | ~50% with more features |
| Custom ($72+/mo) | Business ($199/mo) | 50-70% |
What's Next?
- Set Up Automatic Backups - Protect your data
- Add Team Members - Bring your team over
- Enable Read Replica - High availability (Pro plan)