Migrate from GP Flow to Twenty CRM

GP Flow Contact records map to Twenty People. The contact's first name and last name concatenate into People.name, email populates People.email, phone maps to People.phone, and jobtitle maps to People.jobTitle. Owner assignment resolves by matching the GP Flow owner email to a Twenty workspace member; unmatched owners are flagged for fallback assignment, and the GP Flow contact ID is stored in a custom Source_System_ID__c field to support delta‑run de‑duplication.

GP Flow Company records map to Twenty Companies. Company name populates Company.name, domain maps to Company.domain, and industry maps to Company.industry with value mapping applied for any pick‑list discrepancies. Parent‑company hierarchies use GP Flow’s ParentId field to set Twenty’s Company.parentId, requiring the parent company to be migrated first to maintain referential integrity. The original GP Flow company ID is saved in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow Opportunity records map to Twenty Opportunities. Opportunity name populates Opportunity.name, amount maps to Opportunity.amount, stage maps to Opportunity.stage, and close_date maps to Opportunity.closeDate. Each Opportunity links to its parent Company via Opportunity.companyId, which requires the Company record to exist first. Owner assignment resolves via email match to a Twenty workspace member; the GP Flow opportunity ID is saved in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow custom Fund object maps to a Twenty custom Fund object. Fund name, target_amount, commitment_total, vintage_year, and any other fund‑specific fields are migrated as identically named custom fields on the Twenty Fund object, preserving data types and pick‑list values. The original GP Flow fund ID is stored in a custom Source_System_ID__c field, allowing CapitalCall and Distribution records to reference the correct Fund via Twenty’s relation field type after migration.

Capital call records migrate to a Twenty CapitalCall custom object linked to the Fund and the investor People record. The GP Flow call_amount, call_date, and due_date fields map to identically named fields on the Twenty CapitalCall object, preserving numeric formatting and date precision. The original GP Flow call ID is saved in a custom Source_System_ID__c field for referential integrity with downstream Distribution records and for delta‑run de‑duplication.

Distribution records from GP Flow migrate to Twenty’s Distribution custom object, linked to the Fund and the investor People record via Twenty’s relation field type. Fields such as distribution_amount, distribution_date, and recipient_investor map to identically named custom fields on the Twenty Distribution object, preserving currency formatting and date precision. The original GP Flow distribution ID is stored in a custom Source_System_ID__c field for referential integrity and delta‑run de‑duplication.

GP Flow call activity logs are migrated as Twenty Tasks. The call subject becomes Task.taskTitle, call notes populate Task.body, and the original call timestamp is stored in Task.dueDate to preserve the activity date. Each Task is linked to the related People record via Twenty’s relation field, and the GP Flow activity ID is saved in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow email records are migrated as Twenty Tasks. The email subject line becomes Task.taskTitle, the email body populates Task.body, and any attachments are re‑uploaded to Twenty Files and linked to the Task via Twenty’s file attachment mechanism. The original email timestamp is stored in Task.dueDate to preserve activity timing, and the GP Flow email ID is saved in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow meeting records become Twenty Tasks. The meeting subject maps to Task.taskTitle, the scheduled date becomes Task.dueDate, and meeting notes are written to Task.body. Attendees are linked to the Task via Twenty’s relation fields to People, preserving the attendee roster. The original GP Flow meeting ID is stored in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow notes migrate to Twenty Notes, preserving the note body and original creation timestamp. Each note is linked to its parent record (People, Company, or Opportunity) using Twenty’s noteableId and noteableType fields, ensuring the note appears in the correct record’s timeline. The original GP Flow note ID is stored in a custom Source_System_ID__c field for delta‑run de‑duplication.

GP Flow owner records resolve by email match against Twenty workspace members. If a GP Flow owner has no matching Twenty user, their records attach to a fallback assignee — we flag unmatched owners before migration so you can create or invite the accounts first.

GP Flow file attachments on any record are re‑uploaded to Twenty Files and linked to the corresponding People, Company, Opportunity, or custom object record. File size limits on Twenty apply (default 25 MB per file); we chunk files exceeding this threshold and surface any that exceed the limit for manual handling. The original GP Flow attachment ID is stored in a custom Source_System_ID__c field to track lineage and enable delta‑run de‑duplication.