Migrate from Nurture to Twenty CRM

Nurture Contact records map directly to Twenty Person records. We extract firstname, lastname, email, phone, title, and address fields and map them to their Twenty equivalents. The original Nurture owner (hubspot_owner_id) is preserved in a custom field nurture_original_owner__c on the Person record. If the Nurture export includes lifecycle stage or contact status as a custom property, we map it to a custom select field in Twenty for segmentation continuity.

Nurture Company records map directly to Twenty Company records. The Company record must be created before any Person import because the Person-Company relationship (address field) is a foreign key that must resolve at insert time. We extract domain, industry, employee count, annual revenue, and address fields from Nurture and map them to the corresponding Twenty Company fields. Company name is the dedupe key during import to prevent duplicate Companies.

Nurture Deal records map to Twenty Opportunity records. The deal amount, deal stage, close date, and pipeline assignment migrate directly. We map Nurture pipeline stages to Twenty Opportunity stage values and create a corresponding Pipeline in Twenty's data model before migration. If Nurture stores deal owner as a separate property, we resolve it against the WorkspaceMember mapping.

Each Nurture pipeline and its associated stages are pre-created in Twenty as Opportunity stages before Deal migration begins. We map Nurture stage names to Twenty stage names, preserving probability percentages where Nurture exposes them. The stage configuration is validated in a Twenty Sandbox or test instance before production migration.

Nurture Activity records (calls, emails, meetings, tasks, notes) map to Twenty Task and Event records based on activity type. We use the activity type field from Nurture to determine the mapping: phone activities become Task with a call subtype, email activities become Task with an email subtype, meetings become Event records, and standalone tasks map to Twenty Task. All timestamps (created_at, updated_at) are preserved to maintain the activity timeline order. The linked Contact and Company references are resolved to the migrated Person and Company IDs.

Nurture standalone Task records (to-dos, reminders) map to Twenty Task records. Task subject, description, due date, priority, status, and owner assignments migrate directly. We resolve the Nurture owner ID to the corresponding WorkspaceMember in Twenty and set the Twenty Task's assigned_to field accordingly. Completed status and completion timestamps are preserved.

Nurture custom fields on any standard object (Contact, Company, Deal, Activity) require pre-creation in Twenty's data model before data migration begins. We create each custom field via Twenty's Settings → Data Model panel, selecting the correct field type (text, number, select, multi-select, date, currency, etc.) to match the Nurture data. API names are preserved from Nurture where possible, with underscores replacing spaces. Field order and visibility settings are configured to match Nurture's layout.

Nurture custom objects map to Twenty custom objects created via the /metadata API before migration. We pre-create the destination schema in Twenty, including all custom fields and lookup relationships, then migrate the data through Twenty's GraphQL or REST API. If Nurture custom objects have lookup relationships to standard objects (Contact, Company, Deal), we resolve the parent reference IDs after the standard object migration phase completes.

Nurture Owner records are mapped to Twenty WorkspaceMember records by email address. We extract every distinct owner referenced on Contact, Company, Deal, and Activity records and match by email against the Twenty destination workspace. Any Nurture owner without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer to provision before record import resumes, because OwnerId references are required fields on many Twenty standard objects.

Nurture tags (stored as multi-checkbox or multi-select properties on Contact, Company, or Deal) are mapped to Twenty custom select or multi-select fields. We create the field in Twenty's data model, populate the available options from the Nurture tag values, and import the tag assignments as field values on the respective records. The customer chooses during scoping whether tags should become select fields, separate custom objects, or topic assignments.