Migrate from Grow CRM to Twenty CRM

Grow CRM Contact records map to Twenty People. Standard fields (name, email, phone, address, tags) migrate directly. The contact-to-company relationship resolves via the foreign key at import time: we create Companies first, then map the contact's company reference to the matching Twenty Company record ID. Grow CRM's custom contact fields require pre-creation in Twenty's Settings → Data Model before the CSV import; we extract field definitions from Grow CRM during scoping and document them as a schema specification.

Grow CRM Company records map directly to Twenty Company. Business details (name, domain, industry, address, phone) migrate cleanly. Companies are imported before People so that the relationship lookup is satisfied at the moment of People insert. The domain field becomes the Company Website in Twenty and is used as the dedupe key.

Grow CRM's Lead object (separate from Opportunities) maps to Twenty People if the customer treats unqualified prospects as contact records. If the customer prefers a separate Lead concept, we create a custom object called Lead in Twenty during schema setup and import Grow CRM Leads into that object. Lead status, source, and owner assignment fields are preserved. The customer chooses the Lead strategy during scoping based on their sales process.

Grow CRM Opportunities map to Twenty Opportunities with deal value, stage, expected close date, and owner preserved. Pipeline stages migrate explicitly: we configure the destination Opportunity pipeline with matching stage names before import. Stage probability percentages map to the stage definition in Twenty's pipeline settings. Closed-Lost and Closed-Won reason fields from Grow CRM custom properties become custom Opportunity fields in Twenty.

Grow CRM Tasks map to Twenty Tasks with assignment, due date, status, and description preserved. Grow CRM's custom fields on Tasks are a known migration constraint: custom field definitions are not included in the standard CSV export. We extract field definitions (name, type, options) from the Grow CRM UI or database during scoping, document them as a schema specification, and pre-create matching fields in Twenty's Settings → Data Model before the data import begins. Without this step, custom Task data cannot be imported.

Grow CRM Invoices do not have a direct Twenty CRM standard object equivalent. We create a custom object called Invoice in Twenty with fields for invoice number, line items, total, tax, status, and a lookup to the related People record. Historical paid invoices migrate as closed records; open invoices migrate with their current status and remaining balance. Stripe and PayPal payment history from Grow CRM migrates as a related record under the Invoice custom object or as a Note attached to the People record.

Grow CRM Estimates (quotes or proposals) migrate as a custom object called Estimate in Twenty if the customer has active or historical estimates to preserve. Fields include line items, totals, validity dates, and status. Accepted estimates can be converted to Invoice custom object records post-migration if the customer adopts the invoice workflow. Deprecated or draft estimates with no business value are excluded during scoping.

Grow CRM Help Desk Tickets migrate to Twenty as Case records if the customer has an active support workflow to preserve, or as Note records attached to the relevant People record if the ticket history is informational only. Ticket status, priority, assignee, and conversation history migrate. Conversation threads export as plain text from Grow CRM and preserve as a Note body in Twenty. If the customer requires a full case management workflow, we create a Case object configuration in Twenty before migration.

Grow CRM team member accounts map to Twenty workspace members by email. The customer's admin provisions Twenty workspace invitations before migration begins so that Owner assignments on Opportunities and Tasks can resolve correctly. Grow CRM role definitions are not structurally exportable; we extract the user list and their assigned roles during scoping and document them as a written role configuration plan for the admin to implement in Twenty's workspace settings.

Tags from Grow CRM Contacts, Companies, and Opportunities normalize to Twenty's tag taxonomy during import. Tags stored as comma-separated values in Grow CRM's CSV export are split and recreated as individual tag records in Twenty. We validate tag uniqueness and remove duplicates during the transform step.

Grow CRM custom fields on Clients (Contacts) and Tasks require manual schema reconstruction before import. We extract field definitions from Grow CRM during scoping: field name, field type (text, number, date, select, multi-select), and option values for picklist fields. We then pre-create these fields in Twenty's Settings → Data Model for the relevant object. This step is mandatory; Twenty's CSV import creates records, not fields, and will fail or drop values if the target field does not exist.

Grow CRM Knowledge Base articles export as HTML or markdown content. We export the article title, content, category, and publish status. In Twenty, articles are preserved as Note records attached to the relevant Company or People record, or delivered as a structured document package for the customer to migrate into a dedicated knowledge base tool (Confluence, Notion, or a Twenty-integrated KB platform). Grow CRM's flat article structure is reconstructed with category tags in Twenty.