Migrate from Sales Mantra to Twenty CRM

Sales Mantra Leads map to Twenty CRM Person records with a lead role assignment. The source_lead_id is preserved in a custom field for audit traceability. Lead status values from Sales Mantra are mapped to Twenty's status select options, with any unmapped values added as custom options during the pre-migration field creation sprint. Source attribution fields migrate as text fields in Twenty since there is no native UTM field out of the box.

Sales Mantra Account records map directly to Twenty CRM Company records. The account name, address, industry classification, and any exported custom fields migrate to their Twenty equivalents. The company record is created before any Person import so that the People-Company relationship is satisfied at the moment of Person insert. Industry values are mapped to Twenty's industry picklist or stored as custom select options if the source uses a non-standard taxonomy.

Sales Mantra Deals map to Twenty CRM Opportunity records. Deal name, stage, value, expected close date, and owner assignment migrate. Pipeline stage names vary by Sales Mantra implementation, so we capture the full stage matrix during scoping and map each stage to a corresponding Twenty Opportunity stage with probability percentages. Closed-won and closed-lost reasons from custom properties migrate as custom fields on the Opportunity.

Sales Mantra logged calls migrate to Twenty Task records with TaskSubtype = Call and the original timestamp preserved as ActivityDate. Call duration and disposition fields map to custom number and text fields on the Task. Activity-to-record linking uses Twenty's ActivityTarget object to connect the task to the relevant Person or Opportunity.

Sales Mantra email activity records migrate to Twenty Email records linked via the ActivityTarget relation to the relevant Person, Company, or Opportunity. Email subject, body content, sender, and recipient addresses preserve. If the source export includes email thread references, these are stored as a custom text field to support thread grouping in Twenty.

Sales Mantra meeting logs migrate to Twenty CalendarEvent records with start time, end time, location, and title preserved. Attendee information from the Sales Mantra export maps to CalendarEventParticipant records linked to the corresponding Person records in Twenty.

Sales Mantra task activities (as distinct from logged calls and emails) migrate to Twenty Task records. Status, priority, due date, and description fields map directly. Task assignment migrates by resolving the Sales Mantra owner email to a Twenty User via the user roster mapping.

Sales Mantra notes migrate to Twenty Comment records. Comment body preserves rich text where the export format allows. Comments are linked via the commentableId and commentableType fields to the relevant Person, Company, or Opportunity record. Note timestamps are preserved for timeline ordering.

Sales Mantra's contact classification feature likely uses non-standard field formats or delimited multi-value columns in the CSV export. We audit the export schema during the data audit phase and split any malformed columns into properly normalized fields. Multi-value classifications map to Twenty Tags (via Tag object) with Taggable objects linked to the relevant Person records. Single-value classifications map to custom Select fields created in Twenty's Data Model settings before import. The customer selects the tagging strategy during scoping.

Sales Mantra assigns Deals and Activities to named Owners. The user roster is small (8 employees per Owler data), which makes owner mapping tractable. We extract the user roster from the Sales Mantra export and map Owner IDs to Twenty User records by email match. Any Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Sales Mantra's document management feature attaches files to accounts or deals. The CSV export may contain file references or URLs rather than binary files. We attempt to extract all available document URLs or binary files, but we cannot guarantee all attached documents are reachable without direct platform access. Critical documents should be downloaded manually before migration cutoff. We flag document extraction as a partial-migration item and escalate any unreachable files to the customer for manual handling.

If the Sales Mantra instance uses custom objects beyond the standard Lead-Account-Deal-Activity set, we map each to a Twenty custom object. Twenty allows creation of custom objects from scratch with nested relationship fields. We pre-create the destination schema in Twenty via the Data Model settings, including all custom fields, lookup relationships to standard objects, and any select option values, before any data import begins.