GoldMine to Salesforce migration
We migrate Contacts, Companies, Opportunities, and Communication History from GoldMine into Salesforce with GoldMine's Contact1 and Contact2 structures resolved into Salesforce's Account-Contact relationship model, full activity timeline preserved via Bulk API, and every GoldMine extended-table custom field mapped to a typed Salesforce custom field before cutover.
FlitStack AI migrates accounts, contacts, opportunities, record type + sales process and task + event + emailmessages from GoldMine to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from GoldMine to Salesforce?
GoldMine to Salesforce is a migration from a legacy desktop CRM to a modern cloud platform with fundamentally different data architecture.
Read the full summary
GoldMine stores contacts in a Contact1 (primary) and Contact2 (secondary contact at same company) structure that does not map directly to Salesforce's separate Account and Contact objects. We extract from GoldMine via the XML API or direct SQL reads of the underlying Paradox or SQL Server database, normalize Contact1 and Contact2 records into Account-Contact relationships, and preserve the full communication history as Salesforce Tasks, Events, and EmailMessage records. Custom fields stored in GoldMine's extended columns require pre-migration schema discovery. The GoldMine April 2026 end-of-life deadline makes this migration a hard requirement for organizations still running the platform. Workflows, automations, and GoldMine's built-in reporting do not migrate; we deliver a written inventory of these for your admin to rebuild in Salesforce Setup or Flow.
Contact1 → Account
GoldMine's Contact1 table holds the primary contact and company record.
How it maps
We parse the CompanyName field from each Contact1 record to create a Salesforce Account. The Account's Name maps from GoldMine's Company field or the Contact1 record's company identifier. Account is the parent object created first so that subsequent Contact imports can resolve the AccountId lookup. Deduplication uses Account Name as the external ID with fuzzy matching on variations and abbreviations.
Contact1 → Contact
GoldMine Contact1 records map to Salesforce Contact.
How it maps
The Contact's AccountId lookup is resolved to the Account created from the same GoldMine CompanyName. Name fields (FirstName, LastName) parse from GoldMine's Name1 or separate FirstName/LastName columns depending on the GoldMine version. GoldMine's Title field maps to Contact.Title, and the primary phone block maps to Phone and MobilePhone on the Contact.
Contact2 → Contact (additional per Account)
GoldMine Contact2 records represent secondary contacts at the same company as a Contact1 record.
How it maps
We link each Contact2 record to the same Account as the parent Contact1 by matching on the GoldMine internal RECID or company key. Contact2 fields (name, title, phone, email) map to Contact fields identically to Contact1. If GoldMine Contact2 stores a Role value, we map it to the Salesforce Contact Role object on the Account-Contact relationship. Contacts without an email address are flagged during reconciliation for manual review.
Companies → Account
GoldMine Companies (separate from the company embedded in Contact1) map directly to Salesforce Account.
How it maps
Where GoldMine stores separate Company and Contact records with a linkage between them, we create a single Account from the Company record and link all Contacts that reference that company. If GoldMine uses only Contact1 records without separate Company records, we extract the distinct CompanyName values and create Accounts from those, treating Contact1 as the account-defining record.
Opportunities → Opportunity
GoldMine Opportunities map to Salesforce Opportunity.
How it maps
The GoldMine pipeline stage name maps to a Salesforce StageName that we configure as part of the Record Type and Sales Process setup. GoldMine's Project or deal value maps to Amount, expected close date maps to CloseDate, and Opportunity name maps to Name. If GoldMine stores multiple deal products per opportunity, we create OpportunityLineItem records in Salesforce after resolving the Pricebook2 reference.
Pipeline / Stage → Record Type + Sales Process
Each GoldMine pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that restricts the allowed StageName values to those matching the GoldMine pipeline stages.
How it maps
Stage probability percentages from GoldMine migrate to Salesforce StageProbability values. We configure the Record Type in the destination org before Opportunity migration begins.
- Contact1Account1:1
- Contact1Contact1:1
- Contact2Contactsplit
- CompaniesAccount1:1
- OpportunitiesOpportunity1:1
- PipelineRecord Typetransformed
+ 9 more in the mapping below
How GoldMine and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | GoldMine | Salesforce |
|---|---|---|
| Contact data model | Contact1 (primary) and Contact2 (secondary at same company) flat structure | Separate Account and Contact objects with explicit linking relationship |
| API access | No REST API; XML API DLL or direct SQL Server/Paradox database reads required | Full REST and Bulk API 2.0 with predictable rate limits and OAuth2 authentication |
| End-of-life | Support and updates end April 2026 (Ivanti announcement) | Active development with quarterly releases and 10-year+ support commitments |
| Deployment model | On-premise desktop client with optional nWorkspace cloud hosting | Native cloud SaaS with mobile, desktop, and browser access |
| Custom fields | Stored in extended columns outside the standard UI requiring SQL schema discovery | Custom fields managed through Setup with standard UI, typed fields, and validation rules |
| Activity history | Non-normalized history table with mixed formats (plain text, HTML, MIME-encoded) | Normalized Task, Event, and EmailMessage objects with structured fields and ContentDocument attachments |
| Attachment storage | Network share file paths or database BLOBs, prone to orphaned references | ContentDocument and ContentVersion cloud storage with version history |
What to watch for in a GoldMine to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
GoldMine Contact1/Contact2 structure has no direct Salesforce equivalent
GoldMine's flat Contact1 and Contact2 tables model secondary contacts at the same company without an explicit account object.
How we handle it
Salesforce uses a separate Account-Contact model that requires us to extract CompanyName from each Contact1 record, create a Salesforce Account from it, then link the Contact1 as a Contact on that Account and link each Contact2 as an additional Contact on the same Account. Records where Contact1 and Contact2 are mixed in a single table without a clear company identifier require manual reconciliation before migration. Proseoo's GoldMine vs Salesforce comparison specifically flags that GoldMine's Contact1/Contact2 structure does not translate cleanly to Salesforce's multi-object model. We resolve this during discovery and pre-build the Account-Contact linkage map before any records are imported.
No REST API means extraction depends on database access
GoldMine does not expose a modern REST or GraphQL API.
How we handle it
GoldMine Premium 2024.x uses a SQL Server backend; earlier versions (including GoldMine 2018 still common in many organizations) may use Paradox .DB files. We extract via GoldMine's XML API DLL where the customer's license includes it, or via read-only SQL queries against the GoldMine database with credentials the customer provides. Database access requires the customer to grant SELECT permissions to a dedicated migration account. If the GoldMine database is on a local Paradox backend that cannot be network-accessed, the customer must migrate to SQL Server or cloud-hosted GoldMine before we can extract. Algoworks's migration tips specifically note that knowing how GoldMine's API access works is a prerequisite for successful migration planning.
Communication history encoding and format normalization
GoldMine stores communication history entries in a non-normalized history table with mixed formats: plain text notes, HTML-formatted emails, and MIME-encoded message content sometimes from GoldMine's Outlook COM integration.
How we handle it
We normalize each entry to Salesforce's structured activity model (Task, Event, EmailMessage) and strip encoding artifacts such as multipart MIME boundaries, inline image references that point to deleted attachments, and HTML tags that GoldMine rendered inconsistently. History completeness testing is mandatory before sign-off because silent data loss in the activity timeline is the most common post-migration complaint. Twelve/Three's GoldMine to Salesforce migration guide also emphasizes that matching GoldMine data fields with Salesforce fields is a crucial step to ensure data consistency after migration.
GoldMine end-of-life creates a hard April 2026 migration deadline
Ivanti's end-of-life announcement for GoldMine (April 2026) means organizations must complete this migration before that date or operate unsupported software.
How we handle it
We factor this deadline into project scheduling and flag any scoping that extends into Q1 2026 as requiring expedited scheduling. Customers with large databases, complex custom field inventories, or extensive attachment libraries should begin discovery no later than Q3 2025 to leave adequate migration time. We do not take on GoldMine-to-Salesforce migrations that cannot reasonably complete before the April 2026 deadline because accepting unsupported software risk as part of the migration scope is not consistent with our migration standards.
Custom field discovery must complete before schema design
GoldMine custom fields are stored in extended columns outside the standard GoldMine UI.
How we handle it
A complete custom field inventory requires SQL schema inspection of the CONTACT1, CONTACT2, COMPANIES, and PROJECTS tables to identify all non-system columns. We run this discovery during the first week of the engagement before any Salesforce schema design begins. Custom fields that are discovered late (after Salesforce custom fields have been created and populated) require a retroactive schema change and a data update pass, which adds time and cost. CRM Switch's GoldMine migration best practices specifically list analyzing GoldMine data structure as a step that should not be skipped.
How the migration runs
Discovery and GoldMine database access
We audit the source GoldMine database: version (GoldMine 2018 through 2024.x), backend type (SQL Server or Paradox), record counts per table (CONTACT1, CONTACT2, COMPANIES, OPPORTUNITIES, HISTORY), custom field inventory via SQL schema inspection, active user count, group/list definitions, and any GoldMine Premium Project usage.
What this step covers
We confirm read-only SQL access or XML API availability with the customer's GoldMine administrator. We also identify the target Salesforce edition (Professional at $80/user supports most migrations; Enterprise at $165/user required for custom objects, advanced Flow, or territory management). The discovery output is a written scope and migration plan.
Account-Contact relationship mapping and GoldMine Contact1/Contact2 resolution
We design the GoldMine Contact1/Contact2 resolution strategy.
What this step covers
Every distinct CompanyName value from Contact1 becomes a Salesforce Account. The Contact1 record becomes a Salesforce Contact linked to that Account. Each Contact2 record linked to the same company becomes an additional Contact on the same Account, with any role data mapped to Contact Role. Where Contact2 records lack a clear company identifier, we use the Contact1 parent record or shared phone/address heuristics to resolve the Account link. We document the full Contact-to-Account linkage map and validate it against GoldMine's record counts before extraction begins.
Custom field discovery and Salesforce schema creation
We run a SQL discovery query against the GoldMine database to enumerate all non-system columns across CONTACT1, CONTACT2, COMPANIES, and PROJECTS.
What this step covers
Each custom field is classified by data type and mapped to a Salesforce custom field type (Text, Number, Currency, Date, Picklist). We pre-create all custom fields in the destination Salesforce org via the UI or metadata API with the correct field types and picklist values before any data import. Salesforce validation rules and required-field constraints are documented so we can plan bypasses or data preparation steps for the migration load.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Developer Pro or Full Copy depending on data volume) using production-like record counts.
What this step covers
The customer's admin reviews record counts (Accounts in, Contacts in, Opportunities in, Activities in), spot-checks 25-50 random records against the GoldMine source, and validates that the Contact1/Contact2-to-Account-Contact resolution produced the expected structure. GoldMine Groups and Sales Literature are validated against the sandbox. Any mapping corrections, custom field additions, or Account-Contact linkage adjustments happen in the sandbox before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from GoldMine Companies and Contact1 CompanyName values), Contacts (Contact1 and Contact2 with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activity history (Tasks, Events, EmailMessage via Salesforce Bulk API 2.0 with parent-record lookup resolution), Custom Objects (Projects from GoldMine Premium if applicable), Attachments (ContentDocument via Bulk API with chunked upload for files over 25MB), and finally Tags/Groups as Campaign membership or Lists.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. GoldMine writes are frozen during the cutover window.
Cutover, validation, and automation rebuild handoff
We run a final delta migration of any records modified in GoldMine during the cutover window, then enable Salesforce as the system of record.
What this step covers
We deliver a written inventory of GoldMine workflows, automations, and reporting patterns that require rebuild in Salesforce Setup, Flow, or a reporting partner tool. We do not rebuild GoldMine automations as Salesforce Flow within the migration scope. We support a one-week hypercare window where we resolve any data reconciliation issues raised by the customer's sales team. GoldMine can remain running in read-only mode during hypercare for reference but is decommissioned on customer direction.
GoldMine - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and engagement history size. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for GoldMine to Salesforce →Why teams move from GoldMine to Salesforce
- GoldMine end-of-life is April 2026. Ivanti has announced end-of-support and no further patches or security updates after that date. Organizations still on GoldMine face unsupported software risk, regulatory compliance exposure (especially GDPR and state data breach notification laws), and inability to deploy new integrations. Salesforce provides a long-term support commitment with quarterly releases, 10-year backward compatibility, and explicit enterprise support tiers that removes this deadline pressure permanently.
- Salesforce's cloud-native architecture eliminates the infrastructure dependency GoldMine imposes. GoldMine's COM-based integrations and file-system attachment model require Windows servers and network shares that create both security surface area and operational fragility. Salesforce's cloud API, mobile apps, and native document management remove the need for on-premise Windows infrastructure, which is a meaningful total cost of ownership reduction for organizations currently paying for GoldMine licensing, server hosting, and Windows CALs.
- Reviewers on TrustRadius, G2, and Capterra consistently note that GoldMine's reporting and pipeline visibility are basic compared to Salesforce's reporting engine. GoldMine's built-in reports suit simple contact and activity summaries; Salesforce's reporting supports multi-object joins, cross-territory pipeline analysis, custom fiscal periods, and revenue forecasting with probability-weighted pipeline views. Sales leaders migrating from GoldMine frequently cite improved pipeline visibility as an immediate post-migration benefit.
- GoldMine has no modern REST API, which constrains the entire technology stack. Every integration with GoldMine requires COM automation, the GoldMine XML API DLL, or direct database queries. This architecture makes it impossible to connect GoldMine to modern revenue intelligence tools, sales engagement platforms, marketing automation, or data warehouse pipelines without brittle middleware. Salesforce's REST and Bulk APIs, AppExchange ecosystem of over 9,000 certified apps, and native webhooks eliminate this constraint entirely and open the door to modern RevOps tooling.
- GoldMine's Contact1 and Contact2 flat-file structure does not support the multi-contact-per-account model that modern sales processes require. Salesforce's Account-Contact relationship with Contact Roles on Opportunities, Multiple Contacts per Account (Contacts to Multiple Accounts), and Contact hierarchies enables the granular account management that GoldMine users are missing. TrustRadius reviewers who switched to Salesforce from GoldMine cited improved account intelligence and territory management as primary drivers.
Questions, answered
GoldMine to Salesforce migration questions
How long does a GoldMine to Salesforce migration take?
Most GoldMine to Salesforce migrations land between four and six weeks for organizations with fewer than 15,000 GoldMine records (Contacts, Companies, Opportunities) and clean Contact1/Contact2 structures with moderate activity history. Migrations with large custom field inventories, extensive communication history (over 200,000 GoldMine history entries), GoldMine Premium Project objects, or GoldMine databases on Paradox backends requiring SQL Server migration first move to ten to fourteen weeks because of schema discovery time, encoding normalization, and Bulk API chunking for activity records.
Do GoldMine workflows and automations migrate to Salesforce?
No. GoldMine workflows (GoldMine Premium's process automation rules) and any GoldMine-based email templates or document generation rules do not migrate as code to Salesforce Flow or Salesforce email tools. The automation models are structurally different. We deliver a written inventory of every active GoldMine workflow with its trigger conditions, actions, and a recommended Salesforce Flow equivalent. GoldMine's Sales Literature module migrates as files; GoldMine's mail merge templates are documented for rebuild in Salesforce Sales Cloud's document generation tools or a partner solution like Conga or DocuSign. GoldMine's Outlook COM sync does not have a Salesforce equivalent; the customer configures Salesforce for Outlook or Lightning for Outlook as a separate admin task.
How do we handle GoldMine's April 2026 end-of-life deadline?
We factor the April 2026 end-of-life into project scheduling as a hard constraint. Discovery should begin no later than mid-2025 for organizations with more than 10,000 GoldMine records to leave adequate migration time. We do not scope GoldMine-to-Salesforce migrations that cannot reasonably complete before Q1 2026. Organizations with smaller databases (under 5,000 records) and clean data structures may have more scheduling flexibility, but we still recommend starting discovery early because Salesforce org provisioning, custom field creation, and sandbox testing add timeline before the data migration phases begin.
Can we keep GoldMine running in read-only mode after migration?
Yes. GoldMine can remain installed and accessible in read-only mode after Salesforce goes live so that sales reps can reference historical GoldMine records during the transition period. We recommend a 30-day read-only coexistence window before decommissioning GoldMine, during which the customer's IT team disables GoldMine write permissions and users are directed to Salesforce for all new record creation. Decommissioning GoldMine involves uninstalling the desktop client, terminating the GoldMine license subscription, and either shutting down or repurposing the Windows server that hosted GoldMine's database. We do not manage GoldMine decommissioning as part of the migration scope, but we document the steps.
What happens to GoldMine communication history and attachments?
GoldMine communication history (emails, calls, meetings, notes) is the migration's highest-value and highest-risk object. We migrate the full history as Salesforce Tasks, Events, and EmailMessage records using the Bulk API 2.0 with parent-record lookup resolution (WhoId and WhatId). HTML-formatted GoldMine emails are converted to Salesforce EmailMessage HtmlBody; plain-text notes become Salesforce Note records linked via ContentDocumentLink. Attachments stored as BLOBs or network share files are exported, re-uploaded to Salesforce ContentDocument, and linked to the parent record. Orphaned attachments (where the source file path returns file-not-found) are flagged for the customer's admin to investigate. History completeness is validated against GoldMine record counts before sign-off.
How do we handle GoldMine's custom fields and extended tables?
GoldMine stores custom fields in extended columns linked to primary records by RECID. These are not visible in the GoldMine UI and require SQL schema inspection to enumerate. We run a discovery query during the first week of the engagement that pulls all non-system columns from CONTACT1, CONTACT2, COMPANIES, and PROJECTS. Each custom field is classified by data type and mapped to a Salesforce custom field of the equivalent type. We pre-create Salesforce custom fields before any data import so that custom field data flows into the correct destination fields during migration. Custom fields discovered after Salesforce schema design has begun require retroactive schema changes that add time to the project.
Do we need to migrate GoldMine's Outlook integration to Salesforce for Outlook?
The GoldMine Microsoft Outlook COM integration (synchronized emails, calendar entries, and tasks) has no direct Salesforce equivalent in the core Sales Cloud license. Salesforce offers Salesforce for Outlook (Lightning for Outlook) as a paid add-in that syncs emails and calendar entries between Outlook and Salesforce. Alternatively, organizations can use Salesforce's native email and calendar tools, Salesforce Inbox (a separate paid product), or a third-party sync tool from the AppExchange. We do not configure Salesforce for Outlook as part of the migration scope; we document the existing GoldMine-Outlook sync behavior and the recommended Salesforce replacement path so the customer's admin can configure it post-migration.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Pipedrive to SalesforceMapping · history · rollbackAttio to SalesforceMapping · history · rollbackSugarcrm to SalesforceMapping · history · rollbackAct! to SalesforceMapping · history · rollbackZoho CRM to SalesforceMapping · history · rollbackMailchimp to SalesforceMapping · history · rollback GoldMine to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from GoldMine to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote