Migrate from NeoDeck Holdings to Odoo CRM

NeoDeck patient contact records map to Odoo res.partner entries. Each partner is created as an individual contact with type='contact', preserving the patient's demographic information including name components (firstname, lastname), address details, phone numbers, and email. Any custom clinical properties stored in NeoDeck (such as date of birth, risk tier, or referral source) migrate as x_ prefixed custom fields on the res.partner record, ensuring all patient context carries forward into Odoo without data loss.

NeoDeck provider organization records (including clinics, hospitals, and group practices) map to Odoo res.partner entries created with type='contact' and is_company=True to designate them as company records. Each organization partner preserves the provider's name, website, and primary contact information. Provider-specific attributes such as NPI number, medical specialty, and billing address are stored as custom fields on the company partner record, maintaining the clinical context of each organization in Odoo's CRM.

NeoDeck insurance payer entities (insurance companies, plan administrators) map to Odoo res.partner records with a custom partner_type='payer' tag. Odoo does not have a native payer concept, so we create a custom selection field (x_payer_type) to distinguish payers from clinical contacts and sales accounts.

NeoDeck stores the relationship between a patient and their insurance payer (plan name, member ID, group number) as a property on the contact. These map to custom fields on the patient res.partner record: x_insurance_plan (char), x_member_id (char), x_group_number (char), x_payer_partner_id (many2one to the payer partner).

NeoDeck deal records (including service agreements, licensing contracts, and pipeline opportunities) map to Odoo crm.lead records created with type='opportunity' to distinguish them from raw leads. The crm.lead.name field captures the deal title or description from NeoDeck, planned_revenue maps directly from the deal amount field, and date_deadline corresponds to the target close date. Additional deal-level custom properties such as contract type or implementation milestones also migrate to custom fields on the crm.lead record.

NeoDeck deal status strings (e.g., Prospecting, Proposal, Under Review, Won, Lost) map via value-by-value lookup to Odoo stage_id records. Probability percentages from Odoo's stage configuration are applied per stage. We create the stage records in the target Odoo database before migration runs.

NeoDeck owner (sales rep, account manager, or assigned provider) resolves by email match against Odoo res.users. Unmatched owners are flagged before migration; the customer either pre-creates Odoo users or assigns to a fallback user_id. No crm.lead lands without a responsible user.

NeoDeck custom properties on contacts (e.g., clinical specialty, NPI number, referral source, patient risk tier) migrate as x_ prefixed custom fields on res.partner. Odoo Community requires Developer Mode to create fields; Enterprise exposes a Custom Fields UI. FlitStack delivers a field-creation script as part of the migration package.

NeoDeck deal-level custom properties (such as contract type, license count, implementation milestone flags, and renewal dates) migrate as x_ prefixed custom fields on the crm.lead model. These custom fields preserve the full business context and operational details associated with each opportunity, eliminating the need to reference external systems or maintain separate custom objects in Odoo. The FlitStack migration package includes a custom module manifest that defines all deal-level custom fields before migration execution.

NeoDeck appointment logs, clinical notes, and internal communication entries map to Odoo mail.message records attached to the relevant res.partner or crm.lead. Original author_id (resolved by email match to res.users), create_date, and body text are preserved. Attachments re-upload to Odoo ir.attachment.

Documents attached to NeoDeck patient records, provider records, or deals migrate to Odoo ir.attachment linked to the corresponding res.partner or crm.lead record. File content is Base64-encoded and uploaded via xmlrpc. Odoo's default 25MB per-file limit is enforced; files exceeding this are flagged for manual handling.

NeoDeck user accounts (providers, billing staff, admin) do not map to Odoo res.users in the CRM migration scope. Staff who will use Odoo CRM must be provisioned separately in the target Odoo instance. NeoDeck user IDs are stored on records as x_source_user_id for traceability.