Odoo Partner Handover Checklist: How to secure your database, filestore, Git repo, and Odoo.sh access before switching partners

Steps

1. Request full pg_dump and filestore archive; verify restore on isolated staging within 24 hours.
2. Transfer Odoo.sh project ownership or on-prem SSH keys to customer-controlled accounts; document every deploy key.
3. Clone all custom module repos to your GitHub org; audit __manifest__.py licenses and third-party dependencies.
4. Export list of ir.cron jobs, server actions, and automated actions with XML IDs for replay documentation.
5. Rotate passwords, API keys, EDI mailboxes, payment gateways, and OAuth tokens the old partner accessed.
6. Remove departing partner res.users and portal access; keep read-only audit export of their changes.
7. Sign new partner SOW with 24/7 emergency support for P1 production-down and 30-day risk-free cancellation terms.

Common mistakes

• Letting partner-owned Git be the only copy of custom code.
• Skipping filestore restore test—attachments vanish on cutover.
• Dual partners pushing modules to production the same week.
• No inventory of Studio customizations before uninstall risk.
• Forgot to transfer DNS or SSL for customer portals tied to Odoo website.

Odoo version notes

Handover steps apply to Odoo Community and Enterprise 16–18 on Odoo.sh, on-prem, or cloud VMs. Enterprise license billing stays with your Odoo contract—not the implementer. The ERP Firm Rescue & Run starts with Week 1 Health Audit and 30-Day Top-10 Backlog Guarantee on flat monthly pricing.

When to bring in help

If the fix touches custom modules, regulated traceability, or production outages, a focused rescue sprint beats months of trial and error. See our Odoo service.