Migrate from GoldMine to Twenty CRM

GoldMine Contact records map directly to Twenty CRM People. We extract the CONTACT1 table, handling name parsing (first name, last name, title), phone numbers across multiple phone-type columns, email addresses, and address blocks as standard field-to-field transfers. GoldMine's Additional Contacts stored in separate related rows are merged into a single People record linked to the same Company. The GoldMine RECID becomes a custom external_id__c field on People for relationship resolution during history and attachment migration.

GoldMine Company records map to Twenty CRM Company. Company name, address, phone, website, and industry fields transfer 1:1. We create Company records before People records so that the Company-People lookup relationship is satisfied at the moment of People import. GoldMine Company records that have no associated contacts are imported as standalone Company records with no linked People.

GoldMine Opportunities map to Twenty CRM Opportunity. The GoldMine pipeline stage names and values are reviewed during scoping and mapped to Twenty CRM pipeline stages. We preserve deal value, close date, pipeline name, and stage as custom fields where Twenty CRM's standard Opportunity fields do not cover the customer's specific pipeline logic. The Opportunity-People relationship resolves via the GoldMine contact-opportunity link extracted from the relationship table.

GoldMine stores emails, calls, meetings, and notes as chronological History records tied to Contacts or Companies. These are the highest-value and highest-risk migration objects. GoldMine's history table contains mixed formats: plain text entries, HTML-encoded entries, and MIME-encoded email bodies. We normalize each entry to plain text, strip encoding artifacts, verify character set integrity, and split by type into Twenty CRM Task (for calls, meetings, tasks) and Note (for email body and free-text notes). Activity timestamp is preserved as the Task or Note creation date. The GoldMine RECID cross-reference links each activity to the migrated People or Company record.

GoldMine attachments exist either as BLOBs in the database or as files on a network share referenced by a path in the record. We export attachments with the record they are attached to, re-uploading to Twenty CRM's attachment store and linking to the target People, Company, or Opportunity. Attachments over 25 MB are flagged for chunked upload. Any attachment where the source path returns a file-not-found error is logged to a reconciliation report for the customer to decide: skip, restore from backup, or manually reattach.

GoldMine stores user-defined fields in separate extended columns linked to the primary record by RECID. These extended tables are not visible in the standard GoldMine UI and require SQL schema inspection to enumerate. We run a discovery query that pulls all non-system columns across the CONTACT1 and related tables, classifies each as text, numeric, date, or picklist, and presents the full custom field inventory for mapping. We then create the equivalent custom fields in Twenty CRM Settings → Data Model before any data import runs, per Twenty CRM's requirement that fields must exist before CSV import.

GoldMine Premium Project tracking with tasks, assignments, and milestones maps to Twenty CRM Task and subtask structure. Project-level tasks become parent Tasks with milestones preserved as due dates; individual assignments become child Tasks under the parent. We extract the GoldMine PROJECTS table and TASK table together during discovery to preserve the full project hierarchy before mapping.

GoldMine supports groups, marketing lists, and tag-like labeling on records. We extract group membership lists and apply them as Labels in Twenty CRM on the relevant People and Company records. GoldMine F2 Lookup picklist values that act as tags (e.g., industry classifications, segmentation labels) are mapped to Twenty CRM labels if the customer selects label-based segmentation during scoping.

GoldMine user accounts do not map automatically to Twenty CRM members. We extract the full GoldMine user roster, match by email address against the Twenty CRM Members list, and flag any inactive GoldMine users whose records need reassignment to a current owner. Users must be provisioned in Twenty CRM Settings → Members before the migration begins, per Twenty CRM's requirement that user references must exist at import time.

Appointments synced from Outlook or entered directly in GoldMine are extracted from the GoldMine calendar table and mapped to Twenty CRM Task records with subject, time, attendees, and linked People preserved. Appointment type (call, meeting, demo) is stored as a custom field on the Task. Outlook-synced appointments that GoldMine stores with MIME calendar content are decoded and normalized to plain text for import.