Migrate from SendPulse to Odoo CRM

SendPulse CRM Contacts map directly to Odoo CRM Contacts. Each Contact inherits the linked Company name as the Partner field in Odoo. Standard fields (name, email, phone, custom properties) transfer directly. We deduplicate by email address before import and flag any contacts with missing email addresses for customer review since Odoo requires a valid email format on Partner records.

SendPulse Companies map to Odoo Partners with the Is Company flag set to True. The company-contact linkage in SendPulse translates to Odoo's parent_partner_id relationship — contacts created from SendPulse's linked contact records reference the company Partner. We create Partners before Contacts so the lookup reference is satisfied at insert time. Address fields (street, city, country) transfer to Odoo's contact address fields on the Partner.

SendPulse Deals map to Odoo CRM Opportunities. Deal name becomes the Opportunity name, deal value becomes Expected Revenue, and deal stage maps to an Odoo CRM stage that we configure during schema setup. The responsible user from SendPulse resolves to an Odoo User by email match. Closed-won and closed-lost reasons from SendPulse custom fields migrate to Odoo Opportunity custom fields.

SendPulse Tasks (title, due date, assignee, status, linked contact/company) map directly to Odoo CRM Tasks. Linked entity references in SendPulse resolve to Odoo Partner or Opportunity records during import. Task status (open, completed) maps to Odoo's stage-based task model. We preserve the due date and assignee assignment but note that Odoo task activity types differ from SendPulse's simpler task schema.

SendPulse Subscribers from Mailing Lists are contact records with subscription status variables (subscribed, unsubscribed, bounced). We treat each Subscriber as a Contact record in Odoo and set a custom field email_subscription_status__c to preserve the original state. Multiple SendPulse Mailing Lists may contain the same email address — we deduplicate to a single Odoo Contact and carry a custom field mailing_lists__c listing all originating SendPulse lists. Bounced addresses flag a custom bounced__c field for follow-up validation.

SendPulse Mailing Lists define audience segments with saved filters and dynamic rules. Odoo CRM has no native mailing-list concept, so we create custom Tag records on Partner or Contact for each SendPulse Mailing List name, and set the Tag membership based on the Subscriber-to-List relationship. Dynamic segments with complex conditions cannot be reproduced automatically — we document the segment criteria in the automation inventory for the customer's admin to rebuild using Odoo CRM's filters and segments.

SendPulse CRM Products (name, price, SKU, category) map to Odoo Product Templates with Standard Price. The Product Template is created in Odoo's Inventory app which must be installed alongside CRM. Hidden integration fields from SendPulse (POS IDs, payment gateway metadata stored under the integration_fields parameter) transfer as custom Char fields on the Product Template. We retrieve these via a targeted API call since they do not appear in the standard export UI.

SendPulse campaign statistics (open rate, click rate, bounce data, unsubscribe count) are marketing metrics stored per campaign. Odoo CRM's native reporting focuses on sales pipeline and activity data, not email marketing performance. We import these as formatted notes attached to the related Opportunity, or as custom numeric fields on the Contact, depending on the customer's reporting preference. Delivery statistics should be treated as approximate — SendPulse's moderation and delivery inconsistencies mean some reported opens and clicks may reflect moderation passes rather than actual recipient engagement.

SendPulse verified sender email addresses cannot be transferred to Odoo. Each sender address must be re-verified in the customer's chosen email infrastructure (SMTP server, Mailgun, SendGrid, or Odoo's built-in email alias). We document all SendPulse verified sender domains and addresses as a checklist for the customer's IT team to configure in Odoo's outgoing mail server settings before go-live.

SendPulse Automation 360 flows define multi-step triggered sequences across email and SMS. Odoo Studio provides automations and server actions but the logic model is different. We document every SendPulse Automation 360 flow with its trigger type, conditions, steps, delays, and actions in a written inventory delivered to the customer. The admin rebuilds these manually in Odoo Studio. We do not migrate flows programmatically because SendPulse exposes no API endpoint for flow definitions.

SendPulse chatbots on Telegram, Facebook Messenger, Instagram, WhatsApp, and Viber store flow logic, trigger conditions, and message content in the SendPulse platform. Odoo does not include a native chatbot builder for these channels. Chatbot configurations do not migrate. We document the existing chatbot structure (trigger channels, main flows, key messages) for the customer to evaluate rebuilding in a dedicated chatbot platform or using Odoo's helpdesk bot integration.

SendPulse Landing Pages are self-contained web assets with form fields and CRM logic. Odoo does not have a native landing page builder in the CRM module. Landing pages cannot be exported via API and are not migrated. We recommend Salesforce Web-to-Lead or Odoo's Website builder with Forms as replacement paths, documented in the migration handoff report.