Migrate from GoldMine to HighLevel

GoldMine's primary Contact record maps directly to GoHighLevel Contact. Standard fields (name, phone, email, address, title) transfer as typed fields. GoldMine's RECID becomes a custom field gm_recid__c used for relationship resolution. Contact-to-Company linkage from GoldMine resolves to GoHighLevel Contact-Company relationship or is absorbed into the Contact record if the destination is a single-location setup.

GoldMine Company records map to GoHighLevel Locations or a Company Custom Object depending on the customer's GoHighLevel plan configuration. Company name, address, phone, website, and industry transfer as standard Location fields. We preserve the GoldMine Company-Contact linkage so that each Contact in GoHighLevel references its parent Company via the location_id field.

GoldMine Opportunities map to GoHighLevel Opportunities. The GoldMine pipeline stage names and probabilities migrate to GoHighLevel pipeline stages. We create a GoHighLevel pipeline matching the GoldMine pipeline structure during migration setup. Opportunity amount, close date, probability, and owner transfer as standard fields. GoldMine's custom opportunity fields migrate as custom fields on the GoHighLevel Opportunity object.

GoldMine's history table stores emails, calls, meetings, and notes as chronological records tied to Contacts or Companies. This is the highest-value and highest-risk migration object. GoldMine stores history entries in mixed formats (plain text, HTML, MIME-encoded). We normalize each entry to GoHighLevel's activity format (Activity type, body, timestamp, direction), strip encoding artifacts, and preserve the original direction (inbound/outbound), duration for calls, and subject. Silent data loss here is the most common post-migration complaint and we test history completeness before sign-off.

GoldMine stores custom fields in separate extended columns linked to the primary record by RECID. These extended tables are not visible in the GoldMine UI and require SQL schema inspection to enumerate. We run a discovery query against the GoldMine database that pulls all non-system columns across CONTACT1, COMPANIES, and OPPORTUNITIES tables, classifies each as text, numeric, date, or picklist, and creates the corresponding GoHighLevel custom fields before any data moves. Custom field naming follows GoHighLevel conventions (camelCase with descriptive labels).

GoldMine attachments are stored either as BLOBs in the database or as files on a network share referenced by a path in the record. Network share paths become invalid after migration. We export attachments with the record they are attached to, re-upload to GoHighLevel's document store, and flag any attachment where the source path returns a file-not-found error so the customer can decide whether to skip, restore, or manually reattach. Attachments over 25MB are flagged for chunked upload.

GoldMine user accounts do not map automatically to GoHighLevel users. We extract the full GoldMine user roster, match by email address to existing GoHighLevel users, and flag any GoldMine user without a matching GoHighLevel account for manual provisioning before migration. Inactive GoldMine users are migrated as inactive or reassigned depending on whether their records need an active owner.

GoldMine groups and marketing lists migrate as Tags on GoHighLevel Contacts, or as Smart Lists if the destination GoHighLevel account uses dynamic list segmentation. We extract group membership per Contact and apply the tag during import. If GoHighLevel's Smart List feature is used, we preserve the group membership criteria so the list rebuilds dynamically in GoHighLevel.