Migrate from Myprosperity to Odoo CRM

Myprosperity stores individuals as person records with name, email, phone, address, and a relationship tag. Odoo's `res.partner` model handles both people and organisations — individual clients map 1:1. The Myprosperity `relationship` integer enum (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, etc.) must be decoded and written to Odoo's `function` field or a custom contact-type tag.

Myprosperity company records map to Odoo `res.partner` with `company_type` set to 'company'. The `name` field maps directly; address fields follow Odoo's standard street/city/state/zip structure. If the Myprosperity record links multiple persons to one company, Odoo's `child_ids` relation on the company partner record represents the same hierarchy.

Myprosperity aggregates total assets, total liabilities, and net worth as a client summary. Odoo CRM has no native equivalent. We create custom fields `x_total_assets`, `x_total_liabilities`, `x_net_worth`, and `x_financial_profile_notes` on `res.partner` using Odoo Studio. Data type matches source (monetary fields for dollar amounts).

Each Myprosperity property record (address, type, value, loan amount, loan balance, owner type) becomes a set of custom fields on the linked `crm.lead` in Odoo: `x_property_address`, `x_property_type`, `x_property_value`, `x_loan_original`, `x_loan_balance`, `x_owner_type`. Clients with multiple properties generate multiple opportunity records or use Odoo's inline one2many subview.

Myprosperity vehicle records (registration, make, model, year, value, loan balance) map to Odoo `crm.lead` custom fields: `x_vehicle_registration`, `x_vehicle_make`, `x_vehicle_model`, `x_vehicle_year`, `x_vehicle_value`, `x_vehicle_loan_balance`. Owner resolution on the `partner_id` field links the vehicle record to the correct `res.partner`. Each vehicle associated with a client creates a separate opportunity record in Odoo, or multiple vehicles can be represented as multiple field groups within a single opportunity record depending on the client's Odoo pipeline design.

Myprosperity document store files are downloaded and re-uploaded as Odoo `ir.attachment` records linked to the corresponding `res.partner`. The original filename and create date are preserved. If the Odoo instance runs Enterprise with the Documents app, files route there for full-text search and eSignature workflows.

Annature is Myprosperity's native eSignature partner. Signed documents are retrievable from Myprosperity's document store, but the Annature audit trail (signer identity, timestamp, IP address) has no Odoo Sign equivalent. We re-upload the final signed PDF to Odoo as an `ir.attachment` and flag the record with a custom `x_signed_via_annature` boolean. Rebuilding Odoo Sign envelopes is a manual post-migration step.

Myprosperity Practice Portal staff licences map to Odoo `res.users` accounts. Email-address matching links each Myprosperity owner/staff record to an Odoo user. Myprosperity's Practice Portal roles (admin, adviser, compliance) do not map to Odoo security roles — Odoo access rights must be configured manually post-migration based on the staff member's intended Odoo responsibilities.

Myprosperity notes attached to a client profile migrate as Odoo `mail.message` records on the linked `res.partner` or `crm.lead`. The original author and create timestamp are preserved in Odoo's message metadata. Notes tagged as compliance-related are flagged with a custom `x_compliance_note` tag so advisers can identify them in the Odoo activity stream.

Myprosperity tracks active client engagements as deal records with name, stage, estimated value, and close date. Each engagement maps to a `crm.lead` in Odoo. The Myprosperity deal stage (Prospecting, Quoting, Active, Review) translates to the nearest Odoo CRM stage via value mapping. Estimated value maps to `crm.lead.expected_revenue`; the source deal amount is also written to a custom `x_source_deal_amount` field.

Myprosperity deal pipeline stages (Prospecting, Proposal, Negotiation, Won, Lost) are mapped value-by-value to Odoo CRM stage records. Each Odoo stage must be created in the target CRM before migration runs so the `stage_id` foreign key resolves correctly. Probability and team-assignment fields on the Odoo stage record are set to match the closest Myprosperity stage intent.

Myprosperity integrates with XPLAN (practice management), Macquarie investment feeds, and Xero Practice Manager for data imports. These integrations are platform-specific and do not have Odoo equivalents — they must be rebuilt as Odoo API connections or manual import routines post-migration. We export the current integration configuration as a reference document for your Odoo implementation partner.