Migrate from APTANIA CRM to Odoo CRM

APTANIA Contact records map to Odoo res.partner with type = 'contact'. The B2C/B2B flag from APTANIA's customer-type property migrates as a custom field aptania_customer_type__c on the Odoo partner record. Email, phone, mobile, and address fields map 1:1. We resolve aptania_owner_id to an Odoo User by email match before importing partners so that the user_id (salesperson) field is populated. APTANIA's lifecycle stage or status property migrates as a custom Char or Selection field for reporting continuity.

APTANIA Company records map to Odoo res.partner with type = 'company'. The company-contact linkage is preserved by importing companies first (creating the res.partner record with type='company'), then importing contacts and setting the parent_id (child_of_company) field to the created company partner. Company name becomes the partner display name, and company website maps to website field on the Odoo partner.

APTANIA Deal records map to Odoo crm.lead with type = 'opportunity'. Deal name maps to crm.lead name, monetary value maps to planned_revenue, close date maps to date_deadline, and APTANIA's pipeline stage name maps to Odoo's stage_id via a pre-built stage mapping table. The aptania_contact_id reference resolves to the Odoo res.partner parent_id at migration time. Deal status (open, won, lost) maps to Odoo's probability-based stage probability values.

APTANIA pipeline stages map to Odoo CRM Stage records under a CRM Team. Each APTANIA pipeline becomes a separate CRM Team in Odoo with its own stage sequence. Stage probability values from APTANIA migrate to Odoo's stage probability percentages. If APTANIA uses multiple pipelines, we create corresponding Odoo CRM teams and assign the opportunity to the correct team during import.

APTANIA Activity logs (emails, calls, notes) map to Odoo project.task records under a dedicated migration project. Since APTANIA's activity schema is not publicly documented, we extract what is available in the export file (typically activity type, timestamp, description, and associated contact reference) and map to the Odoo task fields. We flag any unstructured or unparseable activity records in the data map for the customer's admin to review post-migration. Call-type activities set task_subtype = 'call' in Odoo.

APTANIA user records map to Odoo res.users by email address match. APTANIA's role and permission structures do not map directly to Odoo's access-control groups (Sales / User types), so we flag permission differences for manual review. Any APTANIA user without a matching Odoo user email is held in a reconciliation queue for the admin to provision before record import resumes.

APTANIA custom fields are exported with field name and value but the full schema metadata (type, validation, picklist values) may be incomplete. We recreate custom properties in Odoo as ir.model.fields using Char, Selection, or Float types as inferred from the data values. Multi-select custom properties from APTANIA map to Odoo char fields with comma-separated values or to tags (mail.message.subtype) depending on the data pattern. The customer reviews and approves the inferred field types during sandbox validation.

APTANIA email automation rules do not export. We document all active rules from screenshots provided by the customer during scoping and deliver a written inventory that maps each APTANIA trigger condition (field change, inactivity timer, event type) to an Odoo ir.actions.server record or scheduled action. The customer's admin rebuilds the automations in Odoo Studio using the handoff document as the specification. This is out-of-scope as a code migration.

APTANIA's channel attribution data (referrer, UTM parameters, landing page history) does not export via standard tools and is not portable to Odoo. We flag this gap in the data map. For future attribution, we recommend configuring Odoo website tracking (via the Odoo website module with Google Analytics integration) or a third-party tag manager before go-live. Historical attribution data is lost at migration.

APTANIA's Basic plan limits to 1,000 records per month. During scoping, we count total Contact, Company, Deal, and Activity records. If total records exceed 1,000, we recommend upgrading to the Standard (£996/month, 4,000 records) or Enterprise (£1,596/month, 8,000 records) plan before migration begins. Alternatively, we stage the migration across billing cycles: migrate the first batch within the ceiling, then resume after the reset date. We flag over-limit records for the customer to archive or delete before migration.

APTANIA's B2C versus B2B classification lives as a property on Contact records. In Odoo, this does not have a native equivalent since res.partner handles both types. We preserve the classification as a custom Selection field aptania_customer_type__c with values 'B2C' and 'B2B' on the partner record, enabling reporting segmentation after migration.

APTANIA email marketing templates (sent within the platform) are not exported via standard tools. We document the template list visible in APTANIA's UI during scoping and recommend that the customer exports template content manually (copy/paste or screenshot) before migration. Odoo Mail Templates are rebuilt in Odoo's Email Marketing app using the documented content. Template configuration is out-of-scope for data migration.