Migrate from GoldMine to Nutshell

GoldMine Contact records map to Nutshell Person records. The GoldMine CONTACT1 table holds the primary contact fields (name, phone, email, address blocks) and the RECID serves as the dedupe key. We parse composite name fields into first_name and last_name, normalize phone numbers to E.164 format, and use email as the secondary dedupe identifier during Nutshell import. The GoldMine Company-Contact linkage migrates to Nutshell's Company-Person relationship via the COMPANY2 table linkage.

GoldMine Company records map to Nutshell Company records. The GoldMine COMPANY1 table holds the company-level data and links to Contact records through the GoldMine relationship tables. We preserve the Company-Contact linkage so that each Person record is attached to the correct Company in Nutshell. Company names, addresses, phone numbers, and industry fields migrate as standard fields; any GoldMine custom fields on companies map to Nutshell custom fields on the Company object.

GoldMine Opportunities map to Nutshell Deals. The GoldMine PROJECTS or OPMGMT table (depending on GoldMine version and Premium edition usage) stores deal-level records with pipeline stage, value, and expected close date. We review the customer's GoldMine pipeline stage names during scoping, create a corresponding Nutshell pipeline with matching stage values, and map stage probability percentages to Nutshell's expected_probability field. Closed-won and closed-lost statuses migrate with their original close dates preserved.

GoldMine History records (GoldMine HISTORY or SECTIONS table depending on version) store emails, calls, meetings, and notes as chronological entries tied to Contact or Company records by RECID. These are the migration's highest-value and highest-risk object. History entries arrive in mixed formats: some plain text, some HTML, some MIME-encoded email content. We normalize each entry to plain text or HTML depending on Nutshell's activity display format, strip encoding artifacts, verify character set integrity, and set the Activity date to the original GoldMine timestamp. We flag any history record that exceeds Nutshell's activity body field length for manual review before import.

GoldMine appointments synced from Outlook or entered directly in the GoldMine calendar migrate to Nutshell Tasks or Events depending on their type. Meeting-type appointments with attendees become Nutshell Events with the attendee list preserved in the notes field. Single-user tasks and follow-up items become Nutshell Tasks. Appointment subject, time, duration, and linked Contact or Company reference migrate directly. We exclude GoldMine service calendar appointments that have no analog in Nutshell's task model and flag them for the customer's admin to review.

GoldMine attachments are stored either as BLOBs in the database or as files referenced by a path to a network share. Network share paths become invalid after migration and some reference shares that no longer exist. We extract attachments with their parent record, re-upload to Nutshell's document store, and flag any attachment where the source path returns a file-not-found error. We recommend re-uploading attachments larger than 10 MB directly to the customer for verification because network share access may be restricted during the migration window.

GoldMine stores custom fields in extended columns on CONTACT1, COMPANY1, and PROJECTS tables that are invisible in the GoldMine UI. We run a discovery query against the GoldMine database that pulls all non-system columns across these tables, classifies each as text, numeric, date, or picklist, and presents the full custom field inventory for mapping. Each GoldMine custom field becomes a Nutshell custom field on the corresponding People, Company, or Deal object. We coordinate with the customer on picklist value mapping where GoldMine uses user-defined lookup tables for drop-down values.

GoldMine user accounts map to Nutshell User records by email address match. We extract the full GoldMine user roster from the USERS table, match by email against Nutshell users, and flag any GoldMine user whose records need reassignment to an active Nutshell owner. Inactive GoldMine users who own records get reassigned to the customer's primary Nutshell admin during migration. We do not provision Nutshell users; that is done by the customer's Nutshell admin before migration begins.

GoldMine Groups and marketing lists (stored in GoldMine's Group membership tables) migrate to Nutshell Tags applied to the corresponding Person or Company records. We extract the group membership records, resolve each member Person or Company by RECID, and apply the tag to the Nutshell record. Tags preserve the original GoldMine group name so that the customer's marketing lists are searchable in Nutshell after migration. Customers choose whether to consolidate overlapping groups or keep them as separate tags during scoping.