Migrate from Twenty CRM to monday CRM

Twenty Company records map to a dedicated Monday board for accounts. We create a board named after the customer's account structure (e.g., 'Accounts' or 'Companies') and map Twenty fields (name, domain, industry, size, location) to Monday text, dropdown, and number columns. Domain from Twenty's domain field becomes the Website column URL format. Companies must import first because People and Opportunities reference them as linked records.

Twenty People records map to Items within the Account board. Each People record becomes an Item, with name, email, phone, job title, and companyId mapped to corresponding Monday columns. We create a personName column, email column (with link format), phone column (text), and a relation column linking each Person Item to the parent Account Item. This preserves the People-to-Company relationship in Monday's relation-column format rather than as a foreign key.

Twenty Opportunities map to Items on a dedicated Pipeline board. Stage maps to a Status column with values matching Twenty's pipeline stages; amount maps to a Numbers column; closeDate maps to a Date column. We create a relation column linking each Opportunity Item to the parent Account Item and optionally to the associated Person Item. Stage probability percentages from Twenty do not map natively to Monday Status columns; we document these in the mapping notes for the customer to use in custom reporting.

Twenty Tasks map to Items on a Tasks board or as subitems under their parent record (Account, Person, or Opportunity). Title maps to Item name, dueDate maps to a Date column, assignee maps to a Person column or board group owner, and completion status maps to a Status column. Tasks linked to multiple parent records require the customer to decide whether to create duplicate subitems on each parent or consolidate to a single Tasks board with link columns.

Twenty Notes are free-form text attachments linked to People, Companies, Opportunities, or other records. We migrate Notes as Long Text columns on the parent Monday Item, with the note body as content and a date column capturing the original note timestamp. If a Twenty Note is linked to multiple records, we attach it to the primary parent and add a text column noting the additional related records. Notes do not become separate Items because Monday does not have a native note object with independent linkage.

Twenty Custom Objects (e.g., Subscriptions, Events, Rockets) map to dedicated Monday boards. We create a board for each Custom Object and map its fields to typed Monday columns. If a Custom Object has lookups to standard Twenty objects (People, Companies, Opportunities), we create relation columns on the Monday board to replicate those relationships as Monday Item links. Custom Objects capped at 10 on Twenty Pro; Monday Standard and above support unlimited boards and columns.

Twenty pipeline stages map to Monday Status column options on the Pipeline board. We configure the Status column with values matching Twenty's stage names exactly (e.g., 'Prospecting', 'Qualified', 'Demo Scheduled', 'Proposal Sent', 'Closed Won', 'Closed Lost'). Stage probability percentages are not natively supported in Monday Status columns; we document these in a separate column for reference and advise the customer to use Monday's dashboard formulas for probability-based forecasting.

Twenty workspace Members referenced as record owners (on People, Companies, Opportunities, and Tasks) map to Monday Person column values or group assignments. We resolve by email match. Any Twenty Owner without a matching Monday workspace member is held in a reconciliation queue for the customer to provision before record import. Monday Person columns support multiple assignees per Item, which is more flexible than Twenty's single-owner model.

Monday.com has no native activity timeline or engagement object. Call logs, email records, meeting history, and task engagements from Twenty cannot map to a native Monday structure. We offer two options: skip engagement history entirely (the cleanest approach given Monday's data model), or reconstruct selected records as custom columns on the parent Item (e.g., a Long Text column named 'Call Log' with date, duration, and notes). The customer selects the preferred approach during scoping. We do not force-fit engagement history into Monday because it would create unmanageable column bloat and has no native retrieval UI.