Transfer Odoo.sh Licenses to Independent Server

You transfer an Odoo.sh Enterprise license to an independent server by finding your database's unique identifier (database.uuid) in Odoo's technical settings, contacting Odoo's Customer Success Manager to have the enterprise license remapped to your new server, and then migrating the actual database and filestore yourself. This guide explains how to relocate an Odoo Enterprise ERP instance from Odoo.sh to an independent server, since the licensing step and the technical migration are two separate pieces that both need to happen.

Why Would You Move Off Odoo.sh in the First Place?

• Processing timeout limitations
• Cost optimization
• Custom server requirements
• Performance needs

Odoo.sh is a managed hosting platform, which means it trades some control for convenience - it enforces processing timeouts that can affect long-running reports or heavy imports, its pricing scales with the plan tier rather than your own infrastructure choices, and it does not let you install arbitrary system-level packages or tune the server the way a dedicated environment would. None of these are flaws exactly; they are the trade-offs of managed hosting, and they only matter once your business hits one of these limits.

What's Actually Being Transferred Here?

An Odoo Enterprise license is tied to a specific database, identified by its database.uuid, not to the server it happens to run on. Odoo's licensing system needs to know that the enterprise features you are entitled to are now running somewhere else, which is why the transfer is not purely a technical migration - it also requires Odoo to remap the license on their end, or the enterprise apps will stop working on the new server even if the migration itself was flawless.

How Do You Carry Out the Transfer?

1. Access Settings > Technical > System Parameters in your Odoo instance.
2. Find your database.uuid, the identifier your enterprise license is tied to.
3. Contact Odoo's Customer Success Manager to request the license be remapped to your new server before or immediately after cutover.
4. Remap the enterprise license once your new server is confirmed ready.

Alongside the licensing step, you still need to handle the technical side: exporting the database and filestore from Odoo.sh, provisioning and configuring the independent server, and restoring the data there before switching traffic over.

What Should You Watch Out For During the Move?

• Plan downtime window
• Backup all data
• Test on staging first
• Update DNS records

Testing on staging first matters more here than in a typical software update, because you are validating both the technical migration and the license remapping at once. A staging run lets you confirm the enterprise apps still activate correctly on the new server before you commit your production database to the same process.

Frequently asked questions

Will my enterprise apps stop working immediately if I move without contacting Odoo?

Yes, functionally. The license is tied to the database.uuid and its registered hosting, so enterprise features can stop validating if the license is not remapped, even if the underlying data migrated correctly.

How much downtime should I plan for?

This depends on your database size and filestore volume; a planned downtime window sized around your actual data volume, tested first on staging, is safer than assuming the migration will be instantaneous.

Can I move back to Odoo.sh later if the independent server doesn't work out?

The same license transfer principle applies in reverse - contact Odoo's Customer Success Manager to remap the license again, alongside the technical work of migrating the database back.

Who Should Consider This Move?

Businesses that have outgrown Odoo.sh's processing limits, need custom server-level configuration, or want more direct control over infrastructure costs are the ones who typically make this move. If you are evaluating whether to move off Odoo.sh, talk to Simplify-ERP about planning the migration and license transfer together.