Migrate from Goals.com to Twenty CRM

Goals.com Lead records—captured through generation, inquiry, filtering, grading, distribution, and qualification—map to Twenty CRM People records. We preserve the lead's source, status, and assignment by populating Twenty's standard fields (email, name, phone, company) plus any accessible custom metadata. Owner resolution happens via email match against Twenty workspace Members; any unresolved owners go to a reconciliation queue for the admin to address before import.

Goals.com Deals map directly to Twenty CRM Opportunity records. The deal name, value, stage, and close date transfer to Opportunity fields. Pipeline stages from Goals.com are mapped to Twenty stage values, which we configure in Settings before migration. Closed-won and closed-lost reasons migrate as custom text fields since Twenty's standard Opportunity object does not include a dedicated loss-reason field.

Goals.com's native Sales Goals object—tracking call volume, email count, and revenue targets per rep or team—has no direct Twenty CRM equivalent. We model this as custom fields on the Opportunity object (for revenue targets) and on the Company object (for team-level quotas), created in Twenty Settings > Data Model before import. Progress percentages are recalculated post-import in Twenty rather than carried as static values.

Goals.com pipeline stages map to Twenty Opportunity stage values. We configure the stage names and order in Twenty Settings before migration. Each Goals.com stage name becomes a Twenty stage label; the sequence is preserved so that pipeline reporting continuity is maintained.

Goals.com stores organizational data alongside Deals in a flat structure. We extract company-level fields and map them to Twenty Company records. If Goals.com does not have a separate Company object, we derive one from Deal records using the company name field and create Company records during migration to satisfy the Opportunity's companyId lookup in Twenty.

Goals.com User accounts—manager and rep roles—migrate to Twenty CRM workspace Members. We match by email address. Role assignments (manager vs rep) are noted and the customer uses Twenty's role and permission settings to replicate the access hierarchy post-import. If a Goals.com user is referenced on a Deal or Activity but does not exist in Twenty, we hold the record in a reconciliation queue.

Goals.com activity records—notes, reminders, and customer interaction logs—map to Twenty CRM Tasks or Notes. Notes attach to the related People, Company, or Opportunity record via Twenty's linking mechanism. We export the full activity text and timestamp; activity type classification (call, email, meeting) is preserved as a custom field or note body prefix. Goals.com does not store a complete audit trail of every system event, so historical completeness is limited to what is accessible in the export.

Goals.com commission records migrate to a Twenty CRM custom object created during workspace setup. We export commission amount, rep, deal, and calculation date, then import as custom object entries linked to the corresponding Opportunity or People record. Active payout rules, incentive thresholds, and scoring logic do not transfer; we deliver a written commission schema template specifying the fields and logic the customer's admin must re-create manually in Twenty.

Goals.com contest definitions and historical results are exported as a custom object in Twenty CRM. Active contest scoring rules, point allocations, and leaderboard logic are not transferable because they live as platform rules rather than data records. We provide a contest schema template documenting the original contest structure so the customer's admin can rebuild active contests in Twenty.

Goals.com file attachments associated with deals, contacts, or activities are not included in CSV exports for Twenty CRM, per Twenty's documented import behavior. We either migrate attachments via Twenty's GraphQL API where accessible or document each attachment location in a separate file transfer manifest for manual re-upload. The customer receives a manifest listing each record, the attachment name, and the recommended re-upload step.

Goals.com team structures—user groups used for performance visibility and contests—map to Twenty workspace groups. We preserve team membership by linking the migrated User records to their corresponding Twenty workspace Groups. The customer's admin assigns group-level permissions and visibility settings in Twenty after migration.