Migrate from ASPEC to Odoo CRM

ASPEC Contact records map to Odoo res.partner with partner_type='contact'. We extract name, email (email field), phone (phone field), address fields (street, city, state, zip, country), and owner assignment. Owner assignment maps to res.users by email match, with unresolved owners flagged for admin provisioning before the import phase. Tags from ASPEC migrate to res.partner category_id as ir.model.relational_field entries.

ASPEC Company records map to res.partner with partner_type='company'. The company name becomes the partner's name field. We preserve the link between ASPEC Contact and Company as parent_id on the child res.partner record. This requires importing Companies before Contacts in the migration sequence so that the parent_id foreign key resolves at insert time.

ASPEC Opportunities map to Odoo crm.lead records directly. ASPEC deal name maps to name, deal value maps to planned_revenue, expected close date maps to date_deadline, and ASPEC stage name maps to stage_id via the Odoo stage lookup. We configure the Odoo pipeline stages (crm.stage records attached to a crm.team) during the pre-migration schema step so that stage_id references resolve correctly during import.

ASPEC pipeline stage names and ordering are captured during schema discovery and written to Odoo crm.stage records. Each stage gets a sequence number, a probability percentage (we map these from ASPEC if available, otherwise use Odoo defaults), and is assigned to a crm.team. If ASPEC has multiple pipelines, we create multiple crm.team records and assign stage records to the corresponding team.

ASPEC Activity records timestamped to Contacts or Companies migrate to Odoo mail.activity (for scheduled and completed tasks) and mail.message (for logged emails and call records). The res_model on mail.message references res.partner for Contact-linked activities and crm.lead for Opportunity-linked activities. Activity type (call, email, task) maps to activity_type_id via the Odoo activity type configuration. Original timestamps are preserved in write_date.

ASPEC per-user custom fields are stored in a separate metadata layer. We enumerate all active custom fields and their data types during the mandatory schema discovery step, then create matching ir.model.fields entries in Odoo on the target model (res.partner or crm.lead) before any data import begins. Custom field values are extracted from the ASPEC export and written to the new Odoo custom fields. This step is non-negotiable; skipping it results in custom field values being silently dropped during import.

ASPEC Owner records map to Odoo res.users by email address. We extract the full owner list from Contact, Company, and Opportunity records during scoping and match against the destination Odoo instance's res.users table. Any ASPEC owner without a corresponding Odoo user is placed in a reconciliation queue; the customer's Odoo admin provisions the missing user before migration resumes. Archived ASPEC users require the admin to decide whether to reactivate or leave them inactive.

ASPEC tags on Contacts and Companies migrate to crm.tag records in Odoo. The tag names are extracted from the ASPEC export, upserted into crm.tag, and linked to crm.lead via crm.tag.rel (many2many relationship) and to res.partner via res.partner category_id if the customer chooses to surface tags on the partner record.

ASPEC does not expose a documented file attachment export endpoint. We flag all Attachment records during scoping and advise the customer to export them manually via the ASPEC UI or direct download. We then provide a written mapping of which attachment files correspond to which migrated res.partner or crm.lead record, so the customer's Odoo admin can attach them to the correct records post-migration via Odoo's document management interface.

ASPEC Reports are defined in-platform and have no documented export mechanism. We do not migrate Report definitions. During post-migration, the customer's Odoo admin rebuilds reports using Odoo Studio, QWeb report templates, or a BI/reporting tool such as Odoo Spreadsheet or a third-party integration. We deliver a written inventory of every ASPEC report with its filters, groupings, and record scope as a rebuild reference document.

ASPEC Opportunity deal values stored in CAD migrate to Odoo crm.lead planned_revenue as decimal fields. If the customer's Odoo instance uses a different base currency, we document the conversion rate used at migration time in a metadata field so that financial reconciliation is auditable. Price fields in Odoo require a currency_id reference; we set this to the customer's configured Odoo currency at import time.

ASPEC does not have a separate Lead object; unqualified prospects live in the Contact or Company record with a status flag. If the customer uses ASPEC contact status to distinguish marketing leads from sales-qualified contacts, we treat marketing leads as crm.lead records in Odoo (not yet converted) and sales-qualified contacts as res.partner records already linked to an Account. The distinction rule is defined during scoping and applied as a transform step before migration.