Migrate from CASH to Twenty CRM

CASH contacts map to Twenty People records. The People object stores name, email, phone, job title, and a link to the company record via companyId. Owner resolution happens by email match against Twenty Workspace Members before records land, and we preserve the original CASH create timestamp and source system ID in custom fields for audit continuity.

CASH companies map to Twenty Companies records. The Companies object stores name, domain/website, industry, employee count, and address fields. Parent‑child company hierarchies in CASH translate via a custom field pointing to the parent company record in Twenty, and we preserve the original CASH create timestamp and source system ID for audit continuity.

CASH deals map to Twenty Opportunities records. Opportunities track deal name, amount, expected close date, and stage via a custom select field that mirrors CASH pipeline stage values. The opportunity is linked to a Company and optionally to a Person.

CASH custom properties require pre-creation in Twenty's Settings → Data Model before migration. We add each CASH custom property as a Twenty custom field (text, number, select, or multi-select) with the same data type and options. This is the longest planning step for heavily customized CASH workspaces.

CASH engagement logs (calls, emails, meetings) map to Twenty Notes and Tasks. We attach notes with the activity body and timestamp; tasks capture the action item with due date and assignee. Original timestamps and creator email are preserved in custom fields for audit continuity.

CASH file attachments on records re‑upload to Twenty as attachments on the relevant People, Company, or Opportunity record. We preserve the original file name and upload timestamp in custom fields, and we surface any attachments exceeding Twenty's 25 MB default limit for manual handling, logging failures for review.

CASH owner IDs are resolved by email match against Twenty Workspace Members. We flag unmatched owners before migration so your team can invite them to Twenty first, and we store the original CASH owner ID in a custom field for audit traceability. Orphaned owners receive a fallback assignment to a designated admin member.

CASH deal stage pick‑list values are read from the source and created as Twenty custom select options on the Opportunities object. Each stage name maps value‑by‑value, and we preserve the original CASH stage ID in a custom field for reference. Probability percentages are stored as a separate number field for forecasting continuity.

CASH allows labeling contact-to-deal associations (Decision Maker, Influencer, etc.). Twenty has no built-in association labeling — we create a custom select field on the Opportunity record and preserve the label value as a reference for your team to assign in Twenty's UI.

If CASH uses separate lead and contact objects, the lead status pick‑list maps to a Twenty custom select field on the People record. We also map lead source and lead score when present, preserving all original timestamps and status transition dates as custom fields for reporting continuity.