Migrate from The Practice to Odoo CRM

The Practice contacts map directly to Odoo res.partner records. Partner type is set to 'contact' for individuals and 'company' for organization records. Email, phone, and address fields map field-for-field; company-linked contacts receive a parent_id link to the matched company partner.

Organizations in The Practice migrate as res.partner records with partner_type='company'. Child contacts are created as separate res.partner records linked via parent_id. Industry and employee-count fields map to custom fields on the company partner if those Odoo fields are activated in the CRM settings.

Each The Practice pipeline stage maps to a crm.stage record within a specific crm.team. Stage names and display order transfer directly; stage probability values and 'fold' (collapsed in kanban) settings are applied based on Odoo's default probability model per pipeline type.

The Practice notes and activity entries migrate as Odoo mail.message records on the related res.partner or crm.lead. Each message preserves the original timestamp, author (coach), and body text. Mail threads are linked to the partner record so they appear in the Odoo chatter.

Files attached to The Practice contact records are downloaded and re‑uploaded to Odoo ir.attachment via the /web/binary/upload_attachment XML‑RPC endpoint, linked to the corresponding res.partner record using res_model='res.partner' and res_id set to the partner ID. Odoo stores files in its filestore; original filenames and MIME types are preserved, and creation timestamps are kept in a custom Char field on the attachment.

The Practice follow-up reminders and scheduled tasks migrate as planned Odoo crm.activity records linked to the crm.lead or res.partner. Activity type (call, meeting, email) maps to Odoo's activity type taxonomy. Completed vs. pending status is preserved; overdue activities are flagged in Odoo's activity kanban view.

Each custom property in The Practice requires a corresponding ir.model.fields definition in Odoo before import. Field type is inferred from the source data (char for text, selection for pick-lists, integer/float for numeric values). Custom fields are created on res.partner for contact-level properties and on crm.lead for pipeline-specific properties.

The Practice pipeline records map to Odoo crm.lead (opportunity). The lead name becomes crm.lead.name, expected revenue maps to crm.lead.planned_revenue, and pipeline stage maps to crm.lead.stage_id, with probability values inherited from the linked crm.stage record. Owner (user_id) is resolved by email match to res.users, and close date maps to date_deadline. Contact_id links the opportunity to the migrated res.partner record, preserving the original creation date in a custom field.

The Practice staff accounts are matched to Odoo res.users by email address before migration. Unmatched users are flagged in the pre-migration audit; their records are assigned to a fallback owner in Odoo. User active status and Odoo access rights are set post-migration by the Odoo administrator.

If The Practice stores intake form data as a custom object, we create a corresponding custom Odoo model using ir.model and populate it via XML-RPC batch insert. Relationships to res.partner use Many2one fields; the migration plan documents the custom model structure before data lands.

The Practice workflows, automated reminders, and sequence triggers do not have an equivalent in Odoo that preserves logic during migration. These must be rebuilt in Odoo using automated actions (base.automation) and server actions. We export the workflow definitions as a configuration reference for your Odoo admin.

Email templates and client‑facing notification templates from The Practice are not transferred directly. Odoo stores templates in the mail.template model; we export the templates as a CSV/JSON file capturing subject, body, and placeholder tokens. Your Odoo admin can import this file via the /xmlrpc/2/object endpoint to create mail.template records, mapping placeholders to Odoo’s ${object.field} syntax. We provide a mapping so the template logic is preserved in the Odoo template editor.