Migrate from Jubilee to Twenty CRM

Jubilee contacts map 1:1 to Twenty People records. First name, last name, email, phone, and job title transfer directly. Jubilee contact IDs are stored in a custom Source_System_ID__c field on the Twenty record for traceability and delta-run deduplication. All timestamps, including createdAt and updatedAt, are preserved to maintain historical accuracy and support time‑based reporting in Twenty.

Jubilee companies map to Twenty Companies. The domain field enables automatic deduplication via Twenty's domain-matching logic — if a Company with the same domain already exists, records are merged rather than duplicated. Address and industry fields transfer with value-normalization for pick-list fields.

Jubilee's N:N contact-to-company association collapses to a single primary companyId on the Twenty People record. The most-recently-modified company is used as primary by default, or the highest-ranking company per your specified rule. Secondary company associations are preserved as a custom field for reference.

Jubilee deals migrate to Twenty Opportunities. Deal name becomes Opportunity name, amount transfers as a numeric value, and close date maps to the expectedCloseDate field. The pipeline stage name is mapped to Twenty's stage pick-list; if stage names differ between systems, a value-mapping table resolves the translation.

Jubilee deal stage names (e.g. Prospecting, Qualification, Proposal) map to Twenty Opportunity stage values. Probability percentages and forecast category are re-applied based on Twenty's stage configuration. Stage-entered timestamps from Jubilee are preserved in a custom datetime field for reporting continuity.

Jubilee call and email activity logs migrate as Twenty Tasks. The task subject and body carry the activity summary, original create timestamps and owner IDs are preserved, and the due date reflects the activity date. Task status defaults to completed for historical activities.

Jubilee meeting records migrate as Twenty Tasks with type set to 'Meeting'. Start time, end time, and location from the Jubilee meeting are stored in custom fields on the Twenty Task record. Attendees are noted in the task body as a text reference.

Jubilee notes migrate as Twenty Notes. The note body and creation timestamp transfer directly. Notes attached to specific People, Companies, or Opportunities are re-linked in Twenty using the same parent record ID. Rich-text formatting is preserved where the source format is compatible.

Jubilee task assignments map to Twenty Tasks with the assignee set to the matching Twenty workspace member. Owner resolution uses email matching — unmatched owners are flagged before migration and assigned to a fallback workspace member. If a fallback is not specified, records are placed in a dedicated quarantine list for manual review, ensuring no data is lost or misassigned.

Jubilee custom objects map to Twenty custom objects. The schema is reviewed before migration: if a Jubilee custom object uses N:N relationships, Twenty junction objects are created to preserve the same data topology. Custom object import runs after all standard objects to respect foreign-key dependencies.

Jubilee tags and labels migrate to Twenty's tags field on the corresponding object. Tags are stored as a text array in Twenty and appear as filterable chips in the Twenty UI. If Jubilee uses a structured label taxonomy, the full label value is preserved verbatim.

Jubilee owner IDs are resolved by email against Twenty workspace members. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. No record lands in Twenty without a resolved owner reference.