Migrate from GoldMine to Freshsales

GoldMine's primary Contact record maps directly to Freshsales Contact. Standard fields (name, phone, email, address) transfer as typed field-to-field. GoldMine's name parsing splits FirstName and LastName during the transform. We handle duplicate detection via Freshsales' email-based dedupe key. Inactive GoldMine users' contacts are flagged for owner reassignment before import.

GoldMine Company records map to Freshsales Account. The GoldMine Company-Contact linkage preserves as Freshsales' Account-Contact relationship, resolved at migration time by matching the GoldMine CONTACT1.COMPANY or RECID linkage to the Freshsales Account.id. Companies with no linked Contacts create standalone Accounts.

GoldMine Opportunities map to Freshsales Deals. The stage lifecycle differs—GoldMine uses customizable pipeline stages while Freshsales uses a Deal pipeline with stage, probability, and amount fields. We review the customer's GoldMine pipeline stage names during scoping, create a corresponding Freshsales pipeline with matched stage values, and set probability percentages from the GoldMine stage configuration.

GoldMine history records (emails, calls, meetings, notes) are the highest-priority migration objects and the highest risk. GoldMine stores these in a non-normalized table with mixed formats—some plain text, some HTML, some MIME-encoded. We normalize each entry to Freshsales' Activity format, stripping encoding artifacts and setting the Activity type (Call, Email, Meeting, Note) from the GoldMine history type field. Original timestamps preserve the activity timeline ordering.

GoldMine appointments synced from Outlook or entered directly map to Freshsales Events with Subject, Start Time, End Time, Location, and linked Contact or Account preserved. Attendees from GoldMine map to Freshsales Event invitees. GoldMine's COM-based Outlook sync means some appointments may exist in Outlook but not GoldMine; we flag this gap for the customer's admin to decide whether to export from Outlook separately.

GoldMine stores custom fields in extended columns linked to CONTACT1 and related tables by RECID, invisible in the standard UI. We run a discovery query against the GoldMine database to enumerate all non-system columns, classify each as text, numeric, date, or picklist, and present the full custom field inventory before migration. Freshsales custom fields are created during the configuration phase, then populated during data load with type-mapped values.

GoldMine attachments exist as BLOBs in the database or files on a network share referenced by a path. Network share paths become invalid post-migration. We extract attachments with their parent record, re-upload to Freshsales' attachment model, and flag any where the source path returns file-not-found. Attachments over 25MB are flagged for customer decision (skip, restore from backup, or manual reattach).

GoldMine groups, marketing lists, and tag-like labels on records map to Freshsales Tags. We extract the group membership records, apply each tag to the corresponding Contact, Account, or Deal during import, and note any GoldMine group that maps to a Freshsales List (for segmentation and email campaigns) versus a Tag (for record labeling).