Migrate from GoldMine to Pipedrive

GoldMine's primary contact record maps to Pipedrive Person. GoldMine stores name components (FirstName, LastName, Company) with phone numbers and address blocks as standard fields. We parse compound name fields where GoldMine stores a full name in a single field, handle GoldMine's Title field as a custom field in Pipedrive (or map to the secondary_title field if the customer uses the Titles feature), and preserve the GoldMine contact's RECID as a custom field goldmine_recid__c for reconciliation. Email address uniqueness is used as the dedupe key during import.

GoldMine Company records map to Pipedrive Organization. We preserve the Company-Contact linkage using Pipedrive's Person-Organization relationship, linking each migrated Person to their parent Organization by matching on the Company name field in GoldMine. If a GoldMine Contact has no linked Company, we create an Organization on the fly using the Contact's company name and link it immediately. Web address from GoldMine maps to the Organization's address field.

GoldMine Opportunities map to Pipedrive Deals. The key design step is converting GoldMine's pipeline stage field (a picklist on the Opportunity record) into Pipedrive's pipeline and stage model. We review the customer's GoldMine stage values during scoping, create corresponding Pipedrive pipeline stages, and map stage probability percentages where they exist in GoldMine. Deal value (Expected_Close, Actual_Close) migrates to Pipedrive's weighted_value or close_date fields depending on stage status.

GoldMine's History records are the highest-value and highest-risk migration object. History entries are stored in a non-normalized table with mixed formats: plain text, HTML, and MIME-encoded email content. We normalize each entry by detecting format (plain text vs HTML vs MIME), stripping encoding artifacts and redundant headers, and classifying by GoldMine's history type code (E for email, C for call, M for meeting, N for note) before creating the equivalent Pipedrive Activity type. ActivityDate is set to the original GoldMine timestamp to preserve chronological ordering. This is the most tested object before sign-off because silent history loss is the most common post-migration complaint for GoldMine migrations.

GoldMine calendar appointments synced from Outlook or entered directly map to Pipedrive Activity with activity_type = meeting. We extract subject, start time, end time, location, and attendee list. Attendees resolve to migrated Person records by email match. If GoldMine appointments reference contacts that have not yet migrated, we queue the appointment and resolve after the Person import completes.

GoldMine stores custom fields in separate extended columns linked to CONTACT1 and PROJECTS by RECID, invisible in the standard UI. We run a discovery query against the GoldMine database that enumerates all non-system columns, classifies each as text, numeric, date, or picklist, and presents the full custom field inventory for mapping before migration. We pre-create the corresponding custom fields in Pipedrive with matching types before any data import. Any GoldMine picklist fields require us to capture the option values and create matching Pipedrive custom field options during the same configuration step.

GoldMine attachments stored as database BLOBs are extracted and re-uploaded to Pipedrive's file store linked to the parent Person, Organization, or Deal. GoldMine attachments stored as file-system paths on network shares require us to validate the path before extraction; shares that are no longer accessible return a file-not-found error and we flag these records for the customer to decide whether to skip, restore from backup, or manually reattach post-migration. Attachments over 25MB are flagged for chunked upload handling.

GoldMine user accounts do not map automatically to Pipedrive users. We extract the full GoldMine user roster, match by email address against Pipedrive destination users, and flag any inactive GoldMine users whose records need reassignment to an active user before migration. If the destination Pipedrive account does not yet have users provisioned, we extract the GoldMine user list and provide it to the customer as a provisioning checklist before record migration begins.

GoldMine groups and marketing lists stored on Contact records map to Pipedrive Labels applied to Person records. We extract all distinct group names from GoldMine's group membership fields, create equivalent Labels in Pipedrive, and apply them during the Person import. If a GoldMine contact belongs to multiple groups, all labels are applied. Group membership is preserved as label data only; the list concept (GoldMine Group as a standalone record type) does not map to a native Pipedrive object and is documented as a label-based approximation.

GoldMine Premium Project records with tasks, assignments, and milestones do not have a direct Pipedrive equivalent. Pipedrive has no native project object. We map Projects to a combination of Deal-linked Activities (tasks as activity_type = task) with milestone dates preserved as close_date on separate milestone Deals or as custom date fields on the parent Deal. The customer chooses the mapping strategy during scoping. If GoldMine Project tasks have user assignments, we resolve the assignee by email to the migrated Pipedrive User and set the Activity owner accordingly.

GoldMine's Sales Literature module stores content used in mail merges and document generation. We export the file content, re-upload to Pipedrive's file store, and link each file to the related Person or Organization record that it was originally associated with in GoldMine. GoldMine does not store which records referenced a given Sales Literature file, so we link by filename pattern matching against contact and company names where available. Files without an identifiable parent record are uploaded to a general Files section and the customer reconciles manually.