Migrate from GoldMine to Zoho CRM

GoldMine's primary contact concept requires decomposition before Zoho import. In GoldMine, company data often lives in the Contact1 table against a Primary Contact; Zoho expects that data in the Accounts module. We split GoldMine contacts into two passes: first, we identify contacts marked as Primary that contain company-level fields (company name, industry, address) and create Zoho Accounts from them; second, we create Zoho Contacts from all GoldMine contacts and link them to the corresponding Account using the Zoho CRM lookup field. Additional contacts in GoldMine are written to the same Zoho Contacts CSV with the AccountId resolved at import time. We flag any GoldMine contact that has no associated company data and create a standalone Zoho Account for it to satisfy the relational integrity requirement.

GoldMine Company records map directly to Zoho Accounts. We use GoldMine's RECID as a dedupe key and CompanyName as the Account Name. The primary address block maps to the Account's address fields. In practice, many GoldMine migrations reveal that Companies are underpopulated because users entered company data into Contact records instead; we address this during the contact-company split phase and create Account records for any company data discovered in the Contact1 table. Accounts are imported before Contacts so that AccountId is available as a foreign key at Contact load time.

GoldMine Opportunities map to Zoho Deals with the deal name, amount, expected close date, probability percentage, and pipeline stage as the primary mapped fields. GoldMine pipeline stages are user-defined per pipeline; Zoho uses a global picklist across all Deal pipelines. During scoping, we present the customer's GoldMine stage names and probabilities and configure Zoho picklist values to match. If the customer uses multiple GoldMine pipelines, we create corresponding Zoho pipelines and assign each Deal to the correct pipeline during import. Probability maps from GoldMine's numeric field to Zoho's Probability field.

GoldMine's History table stores emails, calls, meetings, and notes as chronological records with mixed encoding—some entries plain text, some HTML, some MIME-encoded. We extract History records via direct SQL query, strip encoding artifacts and HTML tags using a normalization script, set the Task Subject to the GoldMine history type, and populate Task fields (Status, Priority, Activity Date, Description) from the GoldMine record. Call disposition and duration migrate to custom Task fields. Meeting-type history entries migrate to Zoho Events with Start DateTime and End DateTime preserved. The original GoldMine timestamp becomes the Zoho Activity Date for chronological ordering. History extraction is the highest-complexity object in this pair and is validated against the source record count before sign-off.

GoldMine attachments are stored as BLOBs in the database or as files on network shares referenced by a path string in the record. Network share paths become invalid after GoldMine is decommissioned. We extract BLOB attachments directly from the database and re-upload to Zoho's WorkDrive-based attachment model, linking each file to the parent Contact, Account, or Deal record. Files stored on network shares that return a file-not-found error are flagged for customer resolution—skip, restore from backup, or manually reattach. Attachments over 25MB are flagged for chunked upload handling.

GoldMine user accounts map to Zoho CRM users by email address match. We extract the full GoldMine user roster including inactive users and their last-login timestamps. Users without an email address (rare, but seen in older GoldMine deployments) are flagged for manual mapping. Active GoldMine users require corresponding Zoho user provisioning before record import; inactive users are imported as Zoho users with Active=false so that their historical records remain owned and traceable.

GoldMine stores custom fields in extended columns on CONTACT1, COMPANIES, and other primary tables. These extended columns are invisible in the GoldMine UI but visible in the database schema. We run a discovery query that enumerates all non-system columns, classifies each by data type (text, numeric, date, picklist), and presents the full inventory for customer review. Text fields map to Zoho Single Line or Multi Line fields; numeric fields map to Zoho Number fields with appropriate precision; date fields map to Zoho Date fields. GoldMine picklist fields (F2 Lookup fields) require pre-creation of the corresponding Zoho picklist values before import because GoldMine enforces no picklist validation and Zoho does.

GoldMine Premium includes a Project tracking module with tasks, assignments, and milestones. If the customer licenses Zoho One, we map GoldMine Projects to Zoho Projects with task-to-subtask and milestone date preservation. If the destination is Zoho CRM standalone without Zoho One, we map GoldMine project tasks to Zoho Tasks with a Project custom field and milestone dates mapped to due date or custom date fields. The mapping approach is confirmed during scoping based on the customer's Zoho license.

GoldMine Groups and marketing lists map to Zoho Tags. We extract group membership per contact and per company and apply the tag strings to the corresponding Zoho Contact and Account records. Tags in Zoho are free-form string labels; we preserve the original GoldMine group name exactly as entered. If a contact belongs to multiple GoldMine groups, all corresponding tags are applied in Zoho.

GoldMine's Sales Literature module stores documents used in mail merges and document generation. We export these files and re-upload them to Zoho's document store, attaching each file to the Zoho Contact, Account, or Deal record that the GoldMine literature reference pointed to. Literature files without a clear parent record are uploaded as standalone Zoho Attachments to a designated staging Account for customer assignment post-migration.