Migrate from Salesflo Engage to Twenty CRM

Salesflo Engage Workers map directly to Twenty People records. Worker fields (name, email, phone, role) map to the corresponding Twenty People fields. The Worker's organizational company (if the worker belongs to the customer's own org) is set as the primary Company link on the People record.

Salesflo Engage Workers who are also system users map to Twenty WorkspaceMembers for CRM access. Email-based matching is the primary key — the Worker's email must be used to invite the user to Twenty before migration so the People record can be linked to the WorkspaceMember.

Salesflo Engage Store records (retail outlets, field locations) map to Twenty Companies. Store name, address, city, state, category, and subcategory fields map to their Twenty Company equivalents. The store's GPS coordinates (latitude, longitude) are preserved as custom number fields on the Twenty Company record.

Salesflo Engage's locationTagging module stores GPS latitude and longitude per store. Twenty has no native map or coordinate field. We create Latitude__c and Longitude__c custom number fields on the Companies object and populate them during migration. The original coordinate precision is preserved as a decimal(10,8) for latitude and decimal(11,8) for longitude.

Operational visits (check-ins, compliance audits, route stops) map to Twenty Tasks. The Visit record's scheduledTime becomes the Task due date, actualTime becomes the completion timestamp, visitType becomes the Task status or a custom field, and outcome becomes the Task description or a custom select field. The related Worker (now a People record) and Store (now a Company record) links are established via Twenty's relation fields.

Salesflo Engage Visits that have an associated deal value or sales outcome are split into Twenty Opportunities. The visit's amount or order value maps to Opportunity.amount, the visitType or outcome maps to a custom Opportunity Stage pick-list, and the Store (now a Company) becomes the Opportunity's company link. Not all Visits qualify — this split is driven by the presence of a non-null amount field on the source Visit record.

Salesflo Engage Dynamic Survey responses are stored per Visit record. The survey's form schema (field labels, field types) is exported as a migration artifact. Each survey field becomes either a custom field on the Twenty Task/Opportunity (if few fields) or a dedicated custom object (if the survey has many fields and complex structure). The mapping plan specifies this before migration runs.

Salesflo Engage Tasks that are not visit-linked (general to-do items assigned to Workers) migrate directly to Twenty Tasks. Title, description, due date, assigned worker (now a People record), and status map to their Twenty equivalents. Completed status in Salesflo Engage maps to Twenty's completed Task status.

Scheduled visits in Salesflo Engage that have not yet occurred become Twenty Tasks with a future due date. The visitType, store link, and assigned worker are preserved. Once the actual visit occurs and is logged, the Scheduled Visit record is updated and the Task's status changes accordingly — this lifecycle is maintained via a custom Status__c field during migration.

Salesflo Engage files attached to Visit records or Store records are downloaded and re-uploaded to Twenty. File size limits are respected per Twenty's storage configuration. Photos taken during field visits via Salesflo Engage's mobile app are stored as attachments on the related Task or Company record in Twenty.

Salesflo Engage workflow definitions (routing rules, approval chains, task-triggered alerts) are exported as a structured JSON document. This document is delivered alongside the migration and serves as a functional specification for rebuilding equivalent automations in Twenty's Settings → Workflows builder. The migration itself carries no workflow data — it must be rebuilt.

Salesflo Engage's analytics module stores per-worker performance data (visit counts, conversion rates, route adherence scores). These aggregate metrics are preserved as custom fields on the corresponding Twenty People record — e.g., Total_Visits__c, Visit_Conversion_Rate__c. Source timestamps are preserved in a Migration_Source__c text field for traceability.