Migrate from ActiveDEMAND to Odoo CRM

ActiveDEMAND Contacts map directly to Odoo CRM Contacts. Standard fields (name, email, phone, company) migrate 1:1. We resolve the Company reference to an Odoo Contact Company record using the Contact's company name as the dedupe key. Brand Custom Field values migrate to Odoo custom Contact fields that we pre-create during schema setup. Multi-community assignments (Senior Living) migrate to an Odoo custom field ad_community__c and are also applied as Tags on the Contact record.

ActiveDEMAND Companies map to Odoo CRM Companies. The company name becomes the Company Name field and is used as the dedupe key. Address fields (street, city, state, country, zip) map to Odoo Company address fields. If a Contact has a company reference, the Company record must be created before the Contact so that the Contact's company_id field can be set during import.

ActiveDEMAND Campaigns (email, funnel, multi-channel) migrate to Odoo CRM Campaigns with campaign name, start and end dates, and status preserved. Campaign type distinction (email vs funnel vs event) maps to Odoo's campaign Type field. Campaign membership (which Contacts were in which Campaign) migrates as Odoo CRM Campaign Subscriptions or Tags on the Contact record.

ActiveDEMAND Funnels (multi-stage buyer journey builder) map to Odoo CRM Opportunity pipeline stages. We export each Funnel's stage definitions and contact-stage assignments, then create Odoo CRM pipeline stages matching the funnel labels. If multiple Funnels exist, each becomes a separate Odoo CRM pipeline (requires Odoo Sales app) or stage group within a single pipeline.

ActiveDEMAND Deals map to Odoo CRM Opportunities. Deal name becomes Opportunity name, amount maps directly, closed date maps to Odoo Expected Closing Date, and stage maps to Odoo Stage. If ActiveDEMAND Deals reference a funnel stage, the mapping routes to the corresponding Odoo pipeline stage we created during funnel setup.

ActiveDEMAND Call Tracking records include source number, destination number, duration, recording URL, and linked Contact. We create Odoo custom fields on the Contact and Lead models (ad_call_source_number__c, ad_call_duration__c, ad_call_recording_url__c) and populate them from the Call Tracking records linked to each Contact. Recording URLs are preserved as text fields. If the customer uses an Odoo VoIP integration, we document the mapping for the integration partner.

ActiveDEMAND Appointments (date, time, status, linked Contact, community reference) migrate to Odoo CRM Calendar Events or Tasks depending on whether the customer has the Odoo Calendar app enabled. Original appointment date and time preserve in the Event start_datetime and stop_datetime fields. Community reference from the Appointment migrates to the ad_community__c field on the related Contact.

ActiveDEMAND Chat Virtual Assistant conversations (timestamps, message text, visitor contact info) migrate as Odoo CRM Lead or Contact notes. We export conversation metadata (date, duration, message count) as a Note body, with the linked Contact resolved via email match. Full chat transcript text migrates as Note content attached to the Contact record.

ActiveDEMAND Brand Custom Fields are account-specific schemas that must be exported before Contact records. We reproduce the field structure as Odoo custom fields on the crm.lead model (for Leads) and res.partner model (for Contacts) before any data load. Field types (text, number, date, dropdown) map to the nearest Odoo field type. Multi-community schemas (Senior Living) may have different field sets per community — we handle these as conditional field creations based on the community property.

ActiveDEMAND Contact Lists and Segments are static lists of Contact IDs. We export each list's member IDs and apply the list name as an Odoo Tag on each Contact record. For segments with dynamic membership criteria, we document the criteria in the handoff inventory so the customer's Odoo admin can recreate the segment using Odoo CRM's domain-based filtering or a saved filter.

ActiveDEMAND Form definitions and field names migrate as a written metadata inventory (form name, field list, field types, submission mapping). The form body (HTML/CSS) is not migrated. We recommend Odoo Website Forms or a third-party form tool (Typeform, JotForm) as the replacement, and we document the field-level mapping so the admin can configure the equivalent field routing in the replacement form tool.

ActiveDEMAND Landing Page templates and URL references migrate as a written inventory (page name, URL, funnel association, form embedded). The page HTML/CSS and script embeds do not migrate. We recommend Odoo Website as the replacement CMS and document the page-to-page mapping with field routing notes.

ActiveDEMAND Automated Workflow definitions (triggers, conditions, steps, actions) export as a written workflow inventory document. Odoo Studio automations use a different event model (action-motif-based triggers) and are not a direct equivalent. We deliver the inventory with each workflow's trigger type, conditions, and actions described in Odoo-compatible language, and the customer's Odoo partner or admin rebuilds them in Odoo Studio post-migration.

File attachments linked to ActiveDEMAND Contacts, Campaigns, or Forms are exported by URL reference. We download files from ActiveDEMAND's media server to local storage, then re-upload to Odoo as IR Attachment records linked to the equivalent Contact or Lead. Filename and MIME type preserve throughout.