Migrate from Promio to Odoo CRM

Promio Leads map directly to Odoo CRM Lead. We preserve Promio's lead source attribution (Google, Bing, Direct) in Odoo Lead's medium_id or a custom field, and the original campaign name in a custom field for reconciliation. Any Promio custom properties discovered in the CSV export headers become Odoo custom fields via Odoo Studio before import. Promio lifecycle_stage is held at the Contact level, not Lead, so unqualified leads retain no lifecycle value until they are converted to a Contact.

Promio Customers require a split: Odoo requires an Account (the company) before a Contact can be created. We extract the customer's company name from Promio as the Account, create the Account first, then create the Contact linked to that Account. Promio's lifecycle stage (New, Active, At-Risk, Lapsed, Lost) migrates as a custom selection field promio_lifecycle_stage__c on the Contact. Promio's reputation scores (aggregated ratings from third-party review sites) migrate as custom float fields on the Contact for post-migration reporting.

Promio classifies customers into five lifecycle segments stored as custom properties. We map these to a custom selection field on Odoo Contact. The values (New, Active, At-Risk, Lapsed, Lost) become Odoo selection options. We do not create a separate Odoo model for lifecycle tracking because Odoo natively handles customer stage through tags, customer_rank, and custom fields rather than a dedicated stage object. The customer's sales team uses this field for segmentation in Odoo's kanban and list views.

Promio Campaigns map to Odoo CRM Campaign (crm.campaign model). Campaign names, associated ad budgets, and performance metrics (impressions, clicks, conversions) migrate as standard Odoo Campaign fields where applicable or custom fields where Odoo's native Campaign model does not cover Promio's attribution metrics. Budget allocation data from Promio becomes a custom monetary field on the Odoo Campaign. Note that Promio's bundled Google Ads and Bing Ads budget data is not the same as Odoo CRM Campaign budget tracking; we flag this distinction in the scope document.

Promio links Google Ads and Bing Ads accounts through its managed-service credential layer. These credentials do not transfer with the CRM migration because they are stored at the ad network level, not in Promio's CRM database. We extract the current campaign structure, budget allocations, and performance history from Promio's export as a reference document and deliver it to the customer for re-onboarding into Google Ads and Bing directly. This is documented as a separate workstream with zero CRM migration cost.

Promio's call-tracking feature stores audio recordings on Promio's own hosting infrastructure and does not include audio files in CSV exports. We cannot migrate call recordings. We do migrate the call metadata (phone number, duration, call disposition, recording URL pointing to Promio-hosted file) as custom fields on the Contact. The customer must download all required recordings from Promio's interface before the migration cutover date. Post-cutover, those URLs will be dead links unless the customer has preserved the audio files independently.

Promio landing pages are served from promio.com subdomains and are not exportable as HTML, redirect-configurable assets, or portable form definitions. We inventory all active Promio landing pages during the extraction phase and deliver a page-by-page rebuild requirements list specifying the page URL, form fields, lead-source attribution logic, and any A/B test variant information available in Promio. The customer's web team or marketing agency rebuilds these in Odoo's website builder or on the customer's own CMS post-migration.

Promio aggregates review monitoring data (overall rating, review site URLs, reputation score) from third-party aggregators into its dashboard. We extract the aggregated scores and source URLs as custom fields on the Odoo Contact record: promio_rating__c (float), promio_review_url__c (char), and promio_review_source__c (selection). These allow the customer to see historical reputation data in Odoo without requiring a separate review monitoring tool, though Odoo's native review management is limited.

Promio allows custom fields on Leads tied to its campaign attribution system. These fields are discovered during the extraction phase by inspecting CSV headers. We create equivalent custom fields via Odoo Studio on the crm.lead model before import. Custom field types (char, float, selection, date) are inferred from the CSV column data and matched to the closest Odoo field type. Any Promio custom fields added after the export date will not be captured unless a second export is run; we recommend scheduling the final export as close to cutover as possible.

Same approach as Lead custom properties. We inspect Promio's Customer CSV headers for any custom columns beyond the standard fields, create matching custom fields on the Odoo res.partner model (Contact context), and map values during the transformation phase. Encoding issues (special characters in Promio property names) are normalized to Odoo's field naming conventions (lowercase with underscores).

Promio ties every customer record to a campaign source (Google Ads, Bing Ads, Organic, Direct) as part of its revenue attribution layer. We preserve this as a custom field x_promio_source__c on Odoo CRM Opportunity. The original Promio campaign name also migrates as x_promio_campaign__c on the Opportunity. This allows the customer's Odoo sales team to report on revenue by original marketing source without relying on Promio's attribution dashboard.

Promio Owner records (sales reps and service crew members) map to Odoo User records by email match. Any Promio Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Promio team structure (if used) maps to Odoo crm_team records; we create one team per Promio owner group during the schema design phase.