Migrate from Perfect Portal to Odoo CRM

Perfect Portal stages require manual Odoo pipeline pre-configuration before migration

Perfect Portal's stage names are fully custom per firm — Intake, Under Review, Settlement, Closed, and any others the firm created. Odoo CRM requires that crm.stage records exist in the target database before crm.lead records can be assigned stage_id values. If the Odoo pipeline stages do not pre-exist with matching names, the migration script cannot resolve stage_id and the records land with a null stage. We deliver a stage-mapping plan as part of the discovery phase so your Odoo admin can create the stages before data lands. Mismatched stage names are the most common cause of migration re-runs in portal-to-CRM migrations.

Matter-to-client relationships require partner_id pre-creation

Odoo CRM's crm.lead model requires a partner_id (many2one to res.partner) for the client link, and Odoo enforces that the partner record exists before the lead can be created. Perfect Portal matters link to clients that may have been created without email addresses or with duplicate names. Our migration sequences res.partner creation before crm.lead creation, resolving duplicate contacts by email match and creating a fallback partner record for matters whose client cannot be resolved. If your Perfect Portal data has a high rate of orphaned matters (no client linked), those records will require a manual resolution step before the full migration runs.

Odoo XML-RPC API rate limits constrain bulk migration throughput

Odoo's xmlrpc/2/api endpoint is rate-limited per Odoo instance configuration, typically 1,000 requests per minute on standard cloud instances and lower on shared hosting plans. A Perfect Portal instance with 50,000 matter records can generate 200,000+ API calls (res.partner creates + crm.lead creates + mail.message writes + custom field writes). Our migration engine batches and throttles requests to stay within Odoo's rate limits. Instances running Odoo Community on low-end hosting may require the migration to run in off-peak hours to avoid HTTP 429 responses that could corrupt the write sequence if not handled with exponential backoff.

Perfect Portal notification workflows have no Odoo CRM equivalent

Perfect Portal's core value proposition is stage-triggered SMS and email notifications to clients when a matter reaches a new stage. Odoo CRM has a notification system tied to Followers on crm.lead records, but it does not natively send SMS on stage transitions. Replicating the Perfect Portal notification workflow requires installing Odoo's SMS module (part of Odoo Enterprise or a third-party SMS gateway integration via ir.config_parameter configuration) and configuring Odoo automation rules on stage_id change events. We export the Perfect Portal notification rules as a rebuild reference document, but the Odoo rules must be authored by your Odoo admin post-migration — they cannot be migrated programmatically.

Third-party referrer access is a separate Odoo Portal setup

Perfect Portal allows real estate agents, mortgage brokers, and other third parties to access a specific matter with client-visible transparency. Odoo CRM does not have a built-in third-party referrer access model. The closest equivalent is Odoo Portal, which is a separate module requiring installation, portal user creation, and access rights configuration. We migrate third-party referrer contacts as res.partner records with a custom flag, but Odoo Portal access — including invitation emails, password reset flows, and per-record access control — must be configured separately after the CRM data is in place. This adds 1–3 days of post-migration setup time depending on access complexity.