Migrate from Launchpad CRM to Odoo CRM

Launchpad Client records map directly to Odoo res.partner with a partner_type set to 'person'. Contact fields (name, email, phone, address) migrate as typed fields on res.partner. Client ID is stored as an external reference field so the Launchpad ID remains traceable after cutover. Deduplication is applied against the most recently updated field value when redundant entries are detected.

Launchpad Case records map to Odoo crm.lead. The Case Number is preserved as a custom field on crm.lead for traceability. Program linkage migrates as custom fields on the opportunity record because Odoo CRM does not have a native program enrollment object. Case status transitions map to crm.stage values with stage_type='case' to distinguish from sales pipeline stages.

Launchpad Program definitions do not have a direct Odoo equivalent. For workforce development migrations, we either create res.company records representing the funding program or configure custom selection fields on crm.lead listing the available programs. Enrollment records link the client to the program via a custom m2m or o2m relationship on crm.lead depending on whether a client can enroll in multiple programs simultaneously.

Service encounters in Launchpad (assessments, counseling sessions, training completions) map to Odoo in one of two ways depending on complexity. Simple service type and date migrate as custom fields on the parent crm.lead. Complex multi-line service histories with multiple dates and types migrate as sale.order.line records linked to a service quotation or as a separate custom model. The customer chooses the approach during scoping based on how service data is queried post-migration.

Launchpad documents attached to clients or cases migrate as ir.attachment records in Odoo. We download file blobs from Launchpad (where accessible via export) and upload them to Odoo via XML-RPC with the correct res_model and res_id pointing to the migrated crm.lead or res.partner. File name and original upload date are preserved in the attachment record. Document type or category migrates as a custom char field on the attachment.

Caseworker notes and case commentary migrate as Odoo mail.message records on the chatter of the target res.partner or crm.lead. Note body migrates as plain text using mail.message body field. Author and creation date are preserved from the Launchpad note record. Notes are imported after the parent record to satisfy the res_id foreign key.

Formal evaluations or skill assessments tied to a case migrate as typed custom fields on crm.lead: assessment name becomes a char field, score becomes a float or integer field, and completion date becomes a date field. If assessment instruments vary widely, we create a custom assessment_type selection field with score and date fields per type. Instrument mapping may require a lookup table during transform.

Employer records in Launchpad used in job-placement workflows map to Odoo res.partner with company_type set to 'company'. The employer flag is set via a custom boolean field is_employer__c to distinguish from standard business contacts. Employer address and contact information migrate as typed fields on res.partner. Job placement linkages from case records reference the employer partner_id on the crm.lead.

Launchpad program-status or employment-placement stages do not map 1:1 to Odoo's default sales pipeline stages. We create a custom stage configuration in Odoo with stage_type='case' to separate workforce development stages from standard sales pipeline stages. Each stage is assigned a name, sequence, and optional fold status matching the original Launchpad stage names. Probability percentages migrate as decimal fields on crm.stage if the customer uses stage-based forecasting.

Launchpad custom fields capturing eligibility flags, compliance codes, and funding sources migrate as typed custom fields on the target Odoo model. We pre-create the destination custom fields via Odoo's Settings > Technical > Custom Fields interface before migration. Field type mapping: boolean flags become odoo.m2o boolean, text codes become char, numeric codes become integer or char depending on format. Picklist-style values map to selection fields with options matching the source taxonomy.

Files linked to any Launchpad record migrate as ir.attachment with res_model and res_id set to the migrated Odoo model and record ID. If the original attachment is a URL rather than a file blob, we store the URL in a custom char field on the attachment record. The ir_attachment relation table is populated after the parent record exists to avoid foreign key constraint violations.

Launchpad caseworker and staff accounts map to Odoo res.users by email match. We extract owner assignments from Launchpad records and resolve them to the destination res.users ID during migration. Inactive users in Launchpad map to inactive Odoo users with login deactivated. Any owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes.