Migrate from Apto to Odoo CRM

Apto contacts map to Odoo res.partner records with type='contact'. The company association in Apto becomes parent_id pointing to the res.partner record created from the Apto company. Multi-company contacts in Apto (N:N) collapse to one primary company partner in Odoo with additional companies recorded in the partner's commercial partner id or as separate child partners.

Apto companies map to Odoo res.partner records with type='company'. Parent-child company hierarchies in Apto (parent_company_id) map to Odoo parent_id on the res.partner record. Circular references are flagged during pre-migration validation and resolved by creating a placeholder parent in Odoo. This ensures hierarchical relationships are preserved even when source data contains circular loops.

Apto deals map to Odoo crm.lead records with type='opportunity'. The deal's pipeline assignment in Apto maps to an Odoo crm.team (sales team) and crm.stage record. Deals with a 'closed won' or 'closed lost' status in Apto receive a stage in Odoo mapped to the corresponding closed stage. All deal properties (amount, priority, close date) migrate as crm.lead fields or custom fields.

Each Apto named pipeline becomes an Odoo crm.team. Each pipeline stage within that pipeline becomes a crm.stage record attached to that team. Since Odoo's default CRM configures one pipeline per team, teams managing multiple Apto pipelines require pre-migration planning to determine whether to consolidate into fewer Odoo teams or request multi-pipeline custom configuration.

Stage names from Apto map value-by-value to Odoo stage records per team. Probability values attached to each stage in Apto migrate as stage probability values in Odoo. Stage-entered timestamps are preserved as custom datetime fields on the crm.lead record since Odoo does not maintain a native stage-transition history log.

Apto logged calls, emails, and tasks map to Odoo crm.activity records with the corresponding activity_type ('call', 'email', 'meeting', 'task'). Original timestamps, owners, and deal associations (crm.lead) are preserved. Apto activity notes map to crm.activity.note field. All activity metadata is retained for complete historical tracking across the migrated dataset.

Files attached to Apto contacts, companies, or deals are re-uploaded to Odoo as ir.attachment records linked to the corresponding res.partner or crm.lead. Binary file content is downloaded from Apto and POSTed to Odoo's /web/binary/attachment URL via XML-RPC. File size limits and filestore pathing follow Odoo's default configuration.

Apto custom fields per object are pre-created in Odoo via Settings > Technical > Models as custom Char, Selection, or Number fields depending on the Apto field type. Custom field values then migrate as standard field writes during the data load. The custom field API name in Odoo follows Odoo's naming convention (e.g., x_custom_field). All custom fields are created before the data migration run begins.

Apto owner assignments on contacts, companies, and deals resolve by email match to Odoo res.users records. Unmatched owners are flagged in the pre-migration audit report with two options: invite the user to Odoo first, or assign records to a fallback Odoo user. No record lands in Odoo without a resolved user_id.

Apto workflow rules, action sets, and automation triggers do not have a direct equivalent in Odoo and are not migrated by FlitStack. We export Apto workflow definitions as a structured JSON document that your Odoo admin can use as a reference when rebuilding rules in Odoo Studio or via the automation menu. This export is delivered alongside the migration report.