Migrate from Getfly CRM to Twenty CRM

Getfly Accounts combine organization-level fields (company name, address, phone) and person-level fields (contact name, email, title) in a single object. We split Getfly Accounts into Twenty's Company and People objects at migration time. The organization-level fields from Getfly populate the Twenty Company record; the person-level fields populate a linked People record. We create the Company first, then create the People record with a link to the Company via the personCompanyId field. A custom field original_getfly_account_id__c on both Company and People preserves the source record ID for reconciliation.

Getfly Products with SKU, pricing, and custom fields migrate to Twenty's custom object capability. We create a Product custom object in Twenty's Settings → Data Model before import, defining fields that match the Getfly Product schema (name, price, sku, and any custom fields). Getfly's detail_custom_fields nested object is flattened into scalar columns. The CSV import creates records in the custom object; all field types (text, number, dropdown, date) are pre-defined to avoid import errors.

Getfly organizes Deals into configurable pipeline stages that are customer-specific. We extract the full stage configuration from Getfly (stage name, order, probability percentage) during export and map each stage to a Twenty Opportunity stage value. Twenty's opportunity model uses a simple stage field; we configure stage values in Twenty's settings to match the Getfly pipeline structure before importing Opportunities.

Getfly Deals map directly to Twenty Opportunities. We map the Getfly deal name to Opportunity name, deal amount to Opportunity amount, stage to the configured Opportunity stage, and pipeline assignment to a Twenty workspace pipeline identifier. Closed-Lost and Closed-Won reason fields from Getfly custom properties become Opportunity custom fields in Twenty.

Getfly Activities (tasks, calls, meetings) map to Twenty Tasks. Activity type (task, call, meeting) is preserved in a custom Task field activity_type__c. Activity date and duration transfer directly. Owner assignment resolves via email-based lookup against the Twenty workspace user table. Activities linked to Getfly Accounts resolve to the corresponding Twenty Company and People records created during the Account split phase.

Getfly Users acting as record owners are resolved by email match against Twenty workspace members. We export the full user roster during scoping and match against Twenty users before record import begins. Any Getfly owner without a matching Twenty user is placed in a reconciliation queue for the customer to provision before that phase of migration resumes. Active versus inactive status is preserved in a custom field original_getfly_owner_status__c.

Getfly attachments referenced by URL are downloaded to local storage during export and re-uploaded to Twenty. We use Twenty's attachment support to re-associate files with the correct Company, People, or Opportunity record. Original filename and URL reference are preserved in a custom field original_attachment_url__c for audit purposes.

Getfly marketing campaigns (name, start/end dates, linked accounts) migrate to Twenty as a custom Campaign object or as tagged Task records depending on the customer's intended use. Campaign membership (which Getfly Accounts were contacted) migrates as tagged Company records with a campaign identifier field. The customer chooses the campaign strategy during scoping.

Getfly custom fields on Accounts and Products are discovered by sampling Product and Account records during export. Because Getfly has no public field schema registry endpoint, we supplement API sampling with a customer-completed field audit questionnaire run from Getfly's admin panel before migration kickoff. All confirmed custom fields are pre-created in Twenty's Settings → Data Model with type-compatible field definitions before any CSV import begins.

Getfly Workflow automations are stored as internal platform configuration with no public export endpoint. They do not migrate via API. We deliver a written inventory of every active Getfly Workflow with its trigger conditions, actions, and recommended Twenty workflow equivalent during the post-migration handoff. The customer's admin rebuilds automations in Twenty post-migration. This is documented scope, not migrated scope.