Migrate from Ascent360 to Odoo CRM

Ascent360 Profile records map to Odoo Partner records. The HubSpot-style unified contact model in Ascent360 maps to Odoo's Partner model, which combines Company and Individual Contact in one record type. Standard fields (name, email, phone, address, city, state, zip, country) migrate directly. Enrichment-derived fields (lifetime value, stay count, last visit date, preference scores) migrate as read-only custom Char or Float fields on the Partner record. We run a pre-migration field audit against a sample export to identify all active custom properties before mapping, because Ascent360 sometimes excludes custom Profile fields from standard bulk exports unless specifically requested.

Ascent360 Segments define audiences using criteria like purchase history, lifetime value tier, demographic attributes, and preferences. Segment logic does not export as executable rules. We reconstruct audience membership by exporting every Profile's tag assignments and segment associations, then creating corresponding Odoo Tags (res.partner.category) and CRM Groups (crm.tag). The customer's marketing team maps segment criteria to Odoo Segment filters post-migration for dynamic audience rebuilding. We document every active segment with its definition during discovery.

Campaign open rates, click rates, delivery rates, conversion data, and send history migrate as structured CSV data for reimport into Odoo's reporting layer. Odoo CRM does not have a native campaign performance dashboard equivalent to Ascent360's campaign analytics. We deliver campaign metrics as a structured import file with campaign name, send date, recipient count, open rate, click rate, and conversion fields that the customer's admin can import into a custom Odoo report model or third-party BI tool.

Ascent360 allows customers to define custom fields on Profiles. These fields are sometimes excluded from standard bulk exports unless specifically requested. We run a pre-migration field audit against a sample export to identify all active custom properties before mapping. Each identified custom property becomes an Odoo custom field (ir.model.fields) on the res.partner model, with field type matched to the source data type (Char for text, Float or Monetary for numeric, Date for date fields, Selection for picklists). Custom field migration order is resolved before any Partner records are imported so the schema is in place.

Profiles and segments carry tags for classification. We migrate tag assignments alongside Partner records by extracting all tag values from the export, creating the corresponding tag records in Odoo (res.partner.category), and linking them via the res_partner_category_rel many2many table during Partner import. Tag names are preserved exactly as they appear in Ascent360 to maintain segment naming continuity.

Ascent360's direct mail channel uses enriched Profile address data. We migrate the address fields (street, city, state, zip, country) as standard Partner address fields. Physical mail assets (design files, print specifications) are not data objects and do not migrate. We flag any Profiles flagged for direct mail opt-in so the customer's admin can configure Odoo's mailing list feature post-migration. Direct mail campaign performance metrics migrate using the Campaign Performance mapping.

Abandoned cart recovery campaigns in Ascent360 are tied to eCommerce integration event logs. The campaign automation logic does not export. We migrate the integration event log (contacts who entered an abandoned cart state, cart value, cart abandonment date) as a custom event log table in Odoo. The customer's admin uses this data to configure Odoo Automations or a third-party abandoned cart app from the Odoo Apps store.

Ascent360 campaign content (email body, SMS text, subject lines) does not export as portable HTML or text objects. We document every active campaign with its template content, timing, audience size, and channel assignment so the customer's admin can reconstruct templates in Odoo Email Templates or a third-party email app. Campaign content itself is preserved in documentation, not in migratable data.

Ascent360's 150+ integrations are connection credentials to external systems (Shopify, WooCommerce, property management systems, POS terminals). These are not data objects to migrate. We migrate the data that these integrations produced in Ascent360 Profiles. The customer reconfigures integrations directly in Odoo Apps or via the Odoo integration connector of their choice post-migration. Integration credentials must be re-entered in the destination platform.

Automated nurture sequences (birthday emails, anniversary reminders, pre-arrival sequences, win-back flows) are platform-native workflow objects in Ascent360 with no documented export mechanism. We do not migrate automations. We document every active automation during discovery with its trigger conditions, audience logic, delay steps, and channel actions, and deliver a written automation-rebuild guide. The customer's admin rebuilds these in Odoo Automations, Server Actions, or a workflow app from the Odoo Apps store.

Ascent360 records email engagement events (opens, clicks, replies) against Profile records. These are derived event records from the Ascent360 processing layer rather than raw SMTP headers. We migrate engagement event summaries (engagement type, timestamp, campaign association) as structured data in a custom Odoo model. Full email body content does not export from Ascent360. The customer's admin uses this engagement history for segmentation in Odoo rather than for a native activity timeline.

Ascent360 does not natively track sales activities (calls, meetings, tasks) as first-class engagement objects the way a CRM does. If the customer has logged sales activity data in Ascent360 (for example, via a connected call tracking or scheduling integration), we migrate this as CRM Activity records in Odoo with activity type, date, duration, and notes preserved. Standard Odoo CRM Activities (calendar events, phone calls, tasks) are created from this migration for teams that used Ascent360 for activity logging.