How do I switch Odoo partners?

Steps

1. Collect Odoo.sh or server SSH, database backup, and DNS if website integrated.
2. Export list of custom modules with licenses and third-party dependencies.
3. Document integrations: API keys, EDI mailboxes, and cron schedules.
4. Revoke old partner portal users and rotate passwords and API secrets.
5. Sign new partner SOW with escalation paths and response tiers.
6. Run Week 1 technical audit: modules, performance, and open bugs.
7. Move request intake to new portal or kanban with prioritized backlog grooming.

Common mistakes

• Losing Git history because repo was partner-owned.
• No backup before partner removes their deploy keys.
• Signing new partner without reading existing technical debt.
• Dual partners making conflicting module changes simultaneously.
• Missing transfer of Studio or automated action documentation.

Odoo version notes

Partner switches are edition-agnostic on Odoo 16–18. Enterprise customers should confirm Odoo subscription billing separation from partner fees. The ERP Firm accepts handovers from offshore and big-SI projects with Rescue & Run onboarding. Allow two to four weeks for stable knowledge transfer.

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.