Migrate from TOTUS Marketing to Twenty CRM

TOTUS Marketing Contact records map to Twenty CRM Person objects. During discovery we explore the TOTUS Contact schema via direct API to identify all standard and custom fields (first name, last name, email, phone, address properties). The Person object in Twenty stores name, email, phone, and linked company as first-class fields. We preserve any custom TOTUS fields as custom fields on the Person object, created via Twenty's /metadata API before import.

TOTUS Marketing Company or Account records map to Twenty CRM Company. We use the TOTUS domain or company name as the dedupe key during import. Company is created before any Person import so that the Person-Company relationship (workspaceMember, domain, employees, address) is satisfied at Person insert. Any TOTUS custom fields on the Account map to custom fields on Company.

TOTUS Marketing Deal records map to Twenty CRM Opportunity. The deal stage maps to Opportunity stageName, pipeline assignment maps to Opportunity pipeline, and deal amount maps to Opportunity amount. We resolve the linked Company and Person lookups at migration time. Any TOTUS custom fields (probability, closed-won date, closed-lost reason) map to custom fields on Opportunity.

TOTUS Marketing pipeline configuration (stage names, probabilities, order) maps to Twenty CRM Pipeline configuration. We extract the pipeline structure from TOTUS via API exploration and recreate it in Twenty before Deal migration. Stage order and probability percentages are preserved. If TOTUS has multiple pipelines, we create multiple Pipelines in Twenty.

TOTUS Marketing email engagements map to Twenty CRM Task records (activity timeline entry) with email content stored in custom fields or as linked records. We preserve sender, recipient, subject, body, timestamp, and any attachments. The Task is linked to the Person (Who) and Company or Opportunity (What) via Twenty's standard relationship fields.

TOTUS Marketing call engagements map to Twenty CRM Task with call disposition, duration, and recording URL preserved in custom fields. Call direction (inbound/outbound) migrates as a custom picklist field. Activity timestamp is preserved from the source record.

TOTUS Marketing meeting engagements map to Twenty CRM Task records with meeting-specific metadata (attendees, location, start/end time) preserved in custom fields. If the meeting includes attendee list, we create TaskAttendee records linked to the Task and the relevant Person records.

TOTUS Marketing note engagements map to Twenty CRM Task records with the note body in the description or as a linked Comment record. We preserve the author, timestamp, and any attachments. Notes attached to specific records (Person, Company, Opportunity) link via Twenty's object relationships.

TOTUS Marketing task engagements (follow-ups, to-dos) map directly to Twenty CRM Task. Status, priority, due date, and assignee migrate. Task assignment resolves via owner email matching against the Twenty User mapping.

TOTUS Marketing Owner records map to Twenty CRM WorkspaceMember. We resolve owners by email match. Any TOTUS Owner without a matching WorkspaceMember in the destination Twenty instance goes to a reconciliation queue for the customer to provision before record import resumes.

TOTUS Marketing custom objects discovered during API exploration map to Twenty CRM custom objects created via the /metadata API. We pre-create the destination schema including all custom fields, relationship fields, and any enum picklists before any data import. Custom object naming follows Twenty's naming conventions. Lookup relationships to standard objects (Person, Company, Opportunity) are resolved at migration time.

TOTUS Marketing tag or label values stored as multi-select properties migrate to Twenty CRM custom multi-select picklist fields. We extract the distinct tag values during discovery and create the picklist options before import. Tags used for segmentation migrate as-is for re-tagging post-migration.