Migrate from Gold-Vision to Freshsales

Gold-Vision Accounts map directly to Freshsales Accounts. Both use the same terminology and schema for standard fields (name, address, industry, owner). Gold-Vision supports unlimited custom fields on Accounts, all of which map to Freshsales custom properties of the appropriate type (text, number, date, picklist). We use the Gold-Vision account ID as an external reference field on the Freshsales Account record for post-migration reconciliation.

Gold-Vision Contacts link to Accounts and carry email, phone, communication history, and custom fields. We preserve the Account-Contact relationship by importing Accounts first, then resolving the Gold-Vision account_id to the Freshsales account_id at Contact insert time. Gold-Vision's unlimited contact model has no direct pricing analog in Freshsales (which prices per user), but there is no record cap in Freshsales itself; we map all contacts regardless of volume.

Gold-Vision Leads are a distinct record type with their own pipeline and status fields, distinct from Contacts. Freshsales also has a separate Leads object. We map Lead_Status, Lead_Score, and any custom lead fields directly to Freshsales Lead properties. If the customer uses Gold-Vision's lead routing to automatically convert leads, we document the equivalent Freshsales assignment rules for the admin to configure post-migration.

Gold-Vision Opportunities sit inside named pipelines with configurable Stages, probability weights, close dates, and monetary values. Freshsales uses Deals (its Opportunity equivalent) with Stage, Amount, Close Date, and Owner. We map pipeline stages to Freshsales Deal stages, preserving probability percentages. Gold-Vision custom opportunity fields map one-to-one to Freshsales custom properties on Deal.

Gold-Vision allows multiple named pipelines with varying stage sequences per organisation. Freshsales uses a single Deal pipeline with configurable stages on the Growth and Pro plans. We consolidate the Gold-Vision pipeline structure into Freshsales' stage model, creating Freshsales Deal stages that correspond to the most-used Gold-Vision pipeline. If the customer uses multiple Gold-Vision pipelines, we document the stage mapping and recommend that the admin recreate secondary pipelines as separate Deal Views or custom modules on Pro/Enterprise.

Gold-Vision Campaigns include multi-stage status tracking and ROI reporting. Freshsales has a Campaigns object with Type, Status, Start Date, End Date, and Budget fields. We export campaign records and member associations. Note that Gold-Vision campaign member tracking (how contacts are associated to campaigns) maps to Freshsales Campaign Members; however, the campaign member's response status field has slightly different value sets in each platform, and we normalise those during the transform phase.

Gold-Vision Quotes carry line items, branding templates, and optional e-sign links. Freshsales does not have a native Quotes object. We export Quote headers and line items as a structured PDF (or CSV attachment), associate it to the corresponding Freshsales Deal, and preserve the e-sign metadata as a URL reference field. Customers who rely heavily on Gold-Vision's quoting workflow should evaluate Freshsales' CPQ add-on separately; we document the quote-to-attachment mapping as a baseline.

Gold-Vision Projects are standalone records with time entries and task hierarchies. Freshsales does not have a native Projects object. We export the project record, its assigned contacts/accounts, project status, and estimated values. Projects become Deals in Freshsales with a project_reference__c custom field and a note documenting the original Gold-Vision project ID. Time entries migrate as Tasks with a project_id__c reference field. Customers with active project management needs should consider using a dedicated project tool alongside Freshsales; we flag this decision point during scoping.

Gold-Vision service desk Tickets support custom fields, conversation threads, and agent assignment. Freshsales uses Cases for support and service desk records. We map ticket status to Freshsales Case Status, priority to Case Priority, and agent assignment to the Freshsales User. Conversation threads migrate as Case thread entries with timestamps preserved. Gold-Vision's custom ticket fields map to Freshsales custom Case fields.

Gold-Vision supports unlimited additional fields on all major objects via its API. We extract the full custom field schema per object during discovery, map each field to a Freshsales custom property of the matching type (text, numeric, date, dropdown), and deploy the property schema into the Freshsales tenant before data migration begins. Field-level validation in Gold-Vision (required fields, format constraints) is documented as a reconciliation checklist for the admin to re-implement in Freshsales field settings.

Emails, calls, and appointments synced from M365 and Outlook in Gold-Vision are logged as Communications against the relevant contact or account. We export the full communication log with timestamps, direction (inbound/outbound), and body content. Each communication type maps to a Freshsales Activity: emails become Activity records with type email, calls become type call, and appointments become type meeting. Activity ordering is preserved by setting the Freshsales activity timestamp to the original Gold-Vision timestamp.

Documents and file attachments stored against Accounts, Contacts, Opportunities, Projects, and Tickets in Gold-Vision export as binary blobs. We re-associate each attachment to the correct migrated record in Freshsales by resolving the Gold-Vision record ID to the Freshsales record ID. Large attachments (over 10 MB per Freshsales limit) are flagged in the reconciliation report for the admin to handle manually or via a file storage alternative.