Migrate from GoldMine to Microsoft Dynamics 365 Sales

GoldMine Contact records map 1:1 to Dynamics 365 Contact. Name fields (FirstName, LastName, FullName), phone numbers, email addresses, and address blocks transfer as standard typed fields. GoldMine's contact custom fields—stored in extended CONTACT1 columns linked by RECID—require schema discovery before mapping. We enumerate all non-system columns across the CONTACT1 table during discovery, classify each as string, integer, decimal, date, or picklist, and present the full custom field inventory for mapping before any record moves. Contact-Company linkage resolves to AccountId on Contact by matching the GoldMine Link-to-Company key.

GoldMine Company records map 1:1 to Dynamics 365 Account. Company name, address, industry classification, annual revenue, and number of employees transfer as standard fields. Company custom fields follow the same extended-table discovery process as Contact custom fields. We create the Account before importing any related Contact so that the AccountId lookup is satisfied at Contact insert time. GoldMine allows a Company to exist without any linked Contact; Dynamics 365 Account behaves the same way.

GoldMine Opportunities map to Dynamics 365 Opportunity. The stage lifecycle differs significantly—GoldMine uses a simpler open-closed stage model while Dynamics 365 Opportunity includes stage probability percentages, forecast category, and record types tied to sales processes. We review the customer's GoldMine pipeline stage names and probability assumptions during scoping and configure matching stage values in Microsoft Dynamics 365 Sales Process before migration. Closed-Lost and Closed-Won dates, deal value, and owner all transfer directly.

GoldMine stores emails, calls, meetings, and notes as chronological History records tied to Contact or Company. These are the highest-risk migration object because the history table contains mixed formats—plain text entries, HTML-formatted emails, and MIME-encoded content. We normalize each history entry to the appropriate Dynamics 365 activity type: emails become Email (EmailMessage) records; call dispositions and durations become Task with TaskSubtype=Call; meetings become Appointment (Event) records; freeform notes become Note. Character set integrity is verified after normalization. Silent history loss is the most common post-migration complaint and we test history completeness against a row-count baseline before sign-off.

GoldMine appointments synced from Outlook or entered directly migrate as Dynamics 365 Appointment records. Subject, Start Time, End Time, Location, and attendees transfer with the GoldMine timestamp preserved in CreatedOn for timeline ordering. We map the GoldMine appointment linked record (Contact or Company) to the Regarding lookup on the Appointment. If the original GoldMine appointment references an attendee who is not in the migrated user roster, we flag that attendee for manual resolution.

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 SharePoint Online (if the customer's Dynamics 365 is connected to SharePoint) or to Dynamics 365's native annotation model, and flag any attachment where the source path returns a file-not-found error so the customer decides whether to skip, restore from backup, or manually reattach. Attachments exceeding 25MB are flagged for chunked upload.

GoldMine user accounts do not map automatically to Dynamics 365 users. We extract the full GoldMine user roster during discovery and match by email address against the destination Dynamics 365 tenant's Azure Active Directory-backed user list. Any GoldMine user without a matching Dynamics 365 user goes to a reconciliation queue; the customer's admin provisions the missing users before record import resumes. Active versus inactive status in GoldMine maps to Enabled versus Disabled in Dynamics 365, and the admin decides whether to activate for migration or mark inactive.

GoldMine supports Groups and marketing lists that label records for segmentation. We extract these as tag or segment data and apply them as Dynamics 365 Topics (with TopicAssignment records) or as Team membership depending on the customer's intended use. If GoldMine Groups function as security teams in the existing workflow, we recommend Teams in Dynamics 365 as the equivalent access-control mechanism. The customer confirms the segmentation strategy during scoping.

GoldMine custom fields exist as extended columns in separate tables linked by RECID. They 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, COMPANIES, and PROJECTS tables, classifies each as text, numeric, date, or picklist, and presents the full inventory before any mapping. Dynamics 365 custom fields are created on the standard Dataverse entity with matching data types before migration. The custom field API names in Dynamics 365 follow Dataverse naming conventions (new_fieldname) and differ from GoldMine's internal column names.