Migrate from Salesflo Engage to Odoo CRM

Salesflo Engage contacts map to Odoo res.partner records. The partner is created with type='contact'. Phone, email, address, and job title fields migrate directly. Field-force attributes (visit frequency, last visit) are stored as custom fields on res.partner. We also map the original Salesflo Engage contact ID to a custom field (x_studio_source_id) for later reference and deduplication.

When Salesflo Engage stores a company-level profile separate from individual contacts, it maps to a res.partner with is_company=True. Child contacts link via parent_id. Multi-company hierarchies in Salesflo Engage map to Odoo's parent_id chain on res.partner. The company name is stored in the name field; additional company metadata such as industry or size can be captured in custom fields if present in the source.

Salesflo Engage scheduled visits become Odoo mail.activity records of type 'meeting' attached to the corresponding crm.lead or res.partner. Original scheduled date/time, assigned user, and location address are preserved in activity fields. Visits without a matched Odoo user are assigned to a fallback owner and flagged for review.

Ad-hoc visit records and dynamic survey submissions in Salesflo Engage have no direct Odoo equivalent. They migrate as mail.activity records of type 'note' with the submission data stored in custom body text fields and response values mapped to custom char or selection fields on crm.lead.

Salesflo Engage task assignments that relate to field work (store visits, shelf checks) can map to project.task if your Odoo instance has the Project app installed. Otherwise they migrate as crm.lead activities with a custom task_description field. We configure this during the pre-migration schema review.

Salesflo Engage GPS coordinates and location tags are preserved as custom float fields x_studio_latitude and x_studio_longitude on res.partner. A x_studio_location_name custom char field captures the location tag text. These fields are created in Odoo before migration begins. They are indexed to support basic geo‑queries, and can be visualized on a map widget if your Odoo theme includes a geo‑map component.

Salesflo Engage user accounts are matched to Odoo res.users by email address. Active users in Salesflo Engage become active users in Odoo. Inactive accounts are migrated as inactive Odoo users. Owner assignment on records resolves via this user map. If a Salesflo Engage user has no matching Odoo account, the record is flagged for admin review before final assignment.

Each distinct Salesflo Engage form or survey becomes one or more custom fields on the crm.lead model. Field type is inferred from the response data type (char, text, selection, integer). Forms with conditional logic are flattened into individual fields; branching logic is documented for manual Odoo configuration.

Contact and visit tags in Salesflo Engage map to Odoo's crm.lead.tag records via the res.partner.category and crm.lead.tag many2many relations. Tags are created on the Odoo side before migration and linked by name. If a tag name already exists in Odoo, it is reused; otherwise a new crm.lead.tag record is created and associated with the relevant contact or lead records.

Salesflo Engage workflow rules and task automations do not migrate. We export a JSON blueprint of every active workflow showing its trigger conditions, action steps, and field dependencies. Your Odoo administrator uses this as a rebuild reference in Odoo's Automate menu (server actions, automated actions, and base.automation rules).