Migrate from WayMore to Odoo CRM

WayMore Contact records map to Odoo Partner records where is_company=false for individual contacts. Name, email, phone, mobile, street, city, state, zip, country migrate as typed fields. We use email as the external ID for deduplication during import. HubSpot's behavioral data (last visited page, session count) stores in custom fields on the Partner record since Odoo Partner has no native behavioral tracking fields.

WayMore Company records map to Odoo Partner records where is_company=true. Company name becomes Partner name, domain becomes Website field. Individual Contact records from WayMore that belong to this Company link as child Partner records (is_company=false) with parent_id pointing to the Company Partner. This parent-child structure in Odoo replicates the WayMore Contact-to-Company association.

WayMore custom contact properties (text, number, dropdown, checkbox) map to Odoo ir.model.fields entries created on res.partner. We create each custom field in Odoo before import, preserving the original field name as the field label and using a snake_case field technical name. Dropdown values in WayMore map to Odoo selection fields; checkbox values become boolean fields.

WayMore custom company properties map to Odoo ir.model.fields on res.partner where is_company=true for those records. Field types are mapped the same way as contact custom fields. If a WayMore account uses the same custom field name on both Contact and Company, we disambiguate with a prefix (e.g., cf_company_industry vs cf_contact_industry) in Odoo.

WayMore tags on Contacts and Companies map to Odoo Partner Tags (res.partner.category). Tags are stored as a many2many relation in Odoo. We export the full tag list from WayMore, create matching tag records in Odoo, then associate tags with the correct Partner records during import using the tag name as the join key.

WayMore email campaign metadata (name, subject, send date, recipient count) migrates as Odoo Note records attached to the relevant Partner records. Campaign content (HTML body, images) does not transfer through CSV; we document the list of campaigns requiring manual content transfer to Odoo Email Marketing or an external email service provider. Email sending history is not portable between platforms due to SMTP header differences.

WayMore SMS campaign records migrate as Note records referencing the contacts who received the SMS. SMS opt-out status (from WayMore contact preferences) maps to Odoo Partner sms_opt_out field or a custom boolean field if the Odoo SMS module is not active. Actual SMS content is documented for manual re-entry in Odoo's SMS module or a connected SMS gateway.

WayMore Automation Workflows govern customer journey behavior with triggers, conditions, and delays. These are not migratable to Odoo because WayMore's visual workflow model has no direct Odoo equivalent in Community edition. We export workflow definitions as a structured JSON document listing each step, trigger type, conditions, and actions. The customer's Odoo admin or implementation partner uses this document to rebuild equivalent logic in Odoo's Automated Actions, Server Actions, or Studio. Workflow execution state (pending delays, queued messages) is lost at cutover.

WayMore dynamic segments (contacts matching rule-based criteria) cannot be replicated as dynamic rules in Odoo Community. We export each segment's current membership list as a static CSV and create a corresponding Partner Tags or a static Partner domain in Odoo for each segment. Tags are the most practical equivalent. If Odoo Enterprise or a third-party segmentation app is in scope, we note the segment logic in the rebuild guide.

WayMore email engagement records (timestamp, subject, direction) migrate as Odoo Note records attached to the relevant Partner. Email body content migrates as Note body text. Since Odoo Community does not have a native email engagement tracking model, we use Note as the activity-of-record. If Odoo email integration (via Outlook or Gmail connector) is active, email history comes in natively going forward rather than from the migration.

WayMore call, meeting, and task engagements migrate as Note records on the relevant Partner. Duration, disposition, and outcome from call records store in custom fields on the Note if the customer requests that level of detail. Odoo's native Calendar module can represent meetings if Odoo Studio or the calendar module is active, but historical meeting records from WayMore are best stored as Notes for audit rather than as Calendar entries that imply future scheduling capability.

WayMore push notification campaign records migrate as Note references, noting the campaign name and send date. Subscriber device tokens are not portable between platforms because push notification infrastructure is platform-specific (Apple Push Notification Service, Firebase Cloud Messaging). We flag device token loss in the migration report and recommend re-enrollment in Odoo's mobile notification module post-migration.

WayMore chatbot AI flows use a visual decision-tree builder. These are not migratable to Odoo. We export the flow structure (node sequence, decision branches, message content) as a structured document and provide a rebuild guide mapping WayMore chatbot nodes to Odoo Studio automation steps or a recommended third-party chatbot integration (e.g., Crampton chatbot connectors on Odoo Apps). Active chatbot sessions do not transfer.

WayMore tracking scripts, pixel configurations, and behavioral visitor profiles (pages visited, session counts, behavioral scoring) are not portable. We document the active tracker configurations and recommend Odoo Marketing Automation event tracking or a third-party analytics integration post-migration. Historical behavioral data remains in WayMore for reference until the account is closed.

WayMore user accounts map to Odoo User records. We export the user list with name, email, and role. In Odoo, users must be explicitly provisioned (name, email, login, password reset). Odoo's access rights model uses the Security tab on each app; we document the WayMore role structure so the customer's admin can assign equivalent Odoo group memberships (User, Manager, etc.) post-migration.

WayMore email templates, images, media files, and chatbot assets cannot be exported via CSV or any documented API. We generate a checklist of all asset types and URLs visible in the WayMore UI and provide a step-by-step manual download guide. Once downloaded, assets are re-uploaded to Odoo (viaAttachments or media library) or to a connected storage service like S3 or Google Drive referenced from Odoo.