Migrate from Sales Journey to Twenty CRM

Sales Journey Contact records map directly to Twenty Person records. We extract name, email, phone, company association, and any custom properties. The email address serves as the dedupe key during import. Twenty Person records are created before Company import so that the foreign-key relationship is satisfied at Company insert time if the Person was created first.

Sales Journey Company records map to Twenty Company records. Standard address, industry, and size fields transfer directly. We preserve the relationship between companies and associated contacts by creating the Company record first, then resolving the companyId reference on each Person record during migration. If the same company appears under multiple spellings, we flag duplicates for the customer's admin to resolve before import completes.

Sales Journey Deal records map to Twenty Opportunity records. Deal name, stage, value, close date, and probability migrate directly. Pipeline stage names from Sales Journey must be mapped explicitly to Twenty's Opportunity stage values (e.g., Sales Journey stage 'Negotiation' may map to Twenty stage 'Negotiation' or a customer-defined equivalent). We create the stage mapping table during scoping and configure Twenty's pipeline before migration.

Sales Journey Lead records map to Twenty Person records with a lead status field. If the lead has not been converted to a Contact in Sales Journey, it migrates as a Twenty Person with the original lead status preserved in a custom field. Lifecycle stage or lead score from Sales Journey migrates to a Twenty custom field for the customer's admin to use in segmentation.

Sales Journey email engagement records migrate to Twenty TimelineEntry records. We preserve email subject, body, sender, recipient, and timestamp. The TimelineEntry links to the corresponding Person record by resolving the contact reference. If Sales Journey stores email opens or link clicks as behavioral data, we audit whether those attributes export cleanly; if not, we flag the gap and migrate the email content only.

Sales Journey call engagement records migrate to Twenty TimelineEntry records with call type. Duration, call disposition, and recording URL (if stored) migrate to custom fields on the TimelineEntry. The original timestamp is preserved to maintain activity ordering. Owner assignment resolves by matching the Sales Journey owner email to a Twenty User.

Sales Journey meeting engagements map to Twenty TimelineEntry records. Start time, end time, location, and attendee list transfer directly. Attendees link to their corresponding Person records via email match. If meeting notes are stored as rich text, they migrate as TimelineEntry body content.

Sales Journey notes migrate to Twenty Comment records linked to the parent record (Person, Company, or Opportunity). Note body migrates as rich text. If attachments are embedded in notes, we flag them for a separate file-level export step since attachment storage location is often separate from the note body in Sales Journey.

Sales Journey pipeline configuration (stage names, stage order, win/loss criteria) migrates as Twenty Pipeline configuration. Stage-level probability and custom fields on each stage require reconfiguration in Twenty since the UI for pipeline settings differs. We set up the Twenty pipeline during discovery and apply the stage mapping table before record migration begins.

Sales Journey Owner references on records migrate by resolving the owner email to a Twenty User. We build a cross-reference table during scoping. If a Sales Journey owner has no matching Twenty User, we hold those records in a reconciliation queue and flag the missing users for the customer's admin to provision before record import resumes.

If Sales Journey supports custom fields on standard objects, we audit every custom field during discovery and map it to an equivalent Twenty custom field. Custom field types, validation rules, and picklist values require explicit mapping to Twenty's field model. We add any discovered custom field to the field mapping table before committing to the migration timeline.

File attachments stored within Sales Journey records may require a separate file-level export step if they are not included in the standard record export. We identify attachment storage location and total file size during scoping. If the export is available, we download attachments and re-upload to Twenty's file storage, linking each file to its parent record via URL reference. If the export is unavailable, we document the gap in the scoping report.