Migrate your GoldMine data

GoldMine's primary contact record is the most stable object in the schema. We migrate contact fields 1:1, handling name parsing, phone numbers, and address blocks as standard field-to-field transfers. Email addresses are normalized before import to avoid duplicates at the destination.

Companies in GoldMine are distinct records that can be linked to multiple Contacts. We preserve the Company-Contact linkage using the destination CRM's Account-Contact relationship model. Company-level fields such as industry, revenue, and address transfer as-is.

GoldMine Opportunities map to Deals or Opportunities in modern CRMs but use a different stage lifecycle. We review the customer's pipeline stage names and values during scoping and create a mapping table so stages translate correctly rather than landing as blank or default values.

GoldMine stores emails, calls, meetings, and notes as chronological History records tied to Contacts or Companies. These are high-value migration objects but vary in format—some as plain text, some as HTML. We normalize them to the destination's activity format and preserve timestamps and ownership.

Appointments synced from Outlook or entered directly in GoldMine can be migrated as Calendar events or Activities depending on destination. We extract the appointment subject, time, attendees, and linked contact, mapping to the equivalent object in the target system.

GoldMine attachments stored in the database or on the local file server require extraction and re-upload to the destination CRM's document store or attachment model. We flag attachments over 25MB for separate handling and verify file integrity post-migration.

GoldMine Premium includes Project tracking with tasks, assignments, and milestones. Where the destination CRM has a native project object, we map tasks to subtasks and preserve milestone dates. If not, we convert Projects to a custom object or to Opportunities with task lists.

GoldMine allows user-defined fields on every record type, stored in separate extended tables. We enumerate all custom fields during discovery, classify their data types, and map them to custom fields or properties in the destination. We flag fields with no clear destination as candidates for holding tables.

GoldMine user accounts do not map automatically to users in modern SaaS CRMs. We extract the full user roster, match by email address, and flag any inactive GoldMine users whose records need reassignment before migration.

GoldMine supports groups, marketing lists, and tag-like labeling on records. We extract these as tag or segment data and apply them as labels in the destination CRM, preserving the group membership logic.

GoldMine's Sales Literature module stores content used in mail merges and document generation. We export these files and re-upload them to the destination's document library, noting which records referenced them so template associations can be rebuilt.