Migrate from Gold-Vision to Salesforce Sales Cloud

Gold-Vision Accounts map directly to Salesforce Account. Gold-Vision stores address, industry, owner, and unlimited custom fields on Account. The Gold-Vision Account ID is preserved in a custom field gv_account_id__c as a cross-reference for reconciliation. Account is the top-level organisational record and must be migrated before any Contact or Opportunity that holds an AccountId lookup, because foreign-key integrity is enforced during Salesforce insert.

Gold-Vision Contacts link to Accounts and carry email, phone, communication history, and unlimited custom fields. Gold-Vision's unlimited-contact model means there is no per-record cap to consider; all Contacts migrate regardless of volume. We preserve the Account-Contact relationship by resolving the Gold-Vision AccountId to the migrated Salesforce Account ID at migration time. Gold-Vision contact tags migrate to a Salesforce multi-select picklist field contact_tags__c.

Gold-Vision Leads are a distinct record type with their own pipeline and status fields, distinct from Contacts. They map directly to Salesforce Lead. The Gold-Vision Lead status values map to Salesforce Lead Status picklist entries, which we configure in the destination org before migration. Gold-Vision Lead_Source and any scoring custom fields migrate to Salesforce Lead_Source and custom score fields respectively. If the customer has already been using Gold-Vision Leads and Contacts interchangeably, we flag this during scoping because the destination model benefits from a clear Lead-Contact separation.

Gold-Vision Opportunities sit inside named Pipelines with configurable Stages, probability weights, close dates, and monetary values. We export the stage sequence and probability percentages and remap them to Salesforce Opportunity StageName and StageProbability fields. Custom opportunity fields map one-to-one. Each Gold-Vision Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the migrated stage values. If Gold-Vision Opportunities reference a Project (common in Gold-Vision's bundled model), we preserve that reference via a custom Opportunity field project_reference__c.

Gold-Vision supports multiple named pipelines per organisation. We capture the full pipeline structure including stage sequence, stage names, and probability weights. Each pipeline becomes a Salesforce Record Type on Opportunity, and each Record Type gets a Salesforce Sales Process that scopes the StageName picklist to the relevant stages only. Stage probability percentages round to Salesforce's allowed integer values.

Gold-Vision Projects are standalone records with time entries and task hierarchies not found as a standard Salesforce object. During scoping, the customer chooses one of two strategies: (1) map Projects to Salesforce Opportunity with custom fields project_start_date__c, project_end_date__c, and project_status__c; or (2) create a custom Project__c object with a lookup to Account and migrate Projects as custom records. Strategy two requires pre-creating the custom object schema before migration. Time entries associated with a Project migrate as Task records with a custom field time_entry_project__c linking back to the Project or Opportunity. We flag this mapping explicitly because it is the most common source of post-migration reconciliation gaps.

Gold-Vision Campaigns include multi-stage status tracking and in-built ROI reporting. We export campaign records and member associations. Note that Gold-Vision campaign member tracking does not use the same data model as Salesforce Campaign Members: Gold-Vision members are linked Contact or Lead IDs; we resolve these to Salesforce Lead and Contact IDs and create the corresponding CampaignMember records. Campaign budgets and ROI figures migrate as custom currency fields if the customer's reporting depends on them.

Gold-Vision Quotes carry line items, branding templates, and optional e-sign links. We export the quote header, line items, and status. If the customer uses Salesforce Sales Cloud Professional or higher, Quote is a standard object and we migrate directly. E-sign metadata (DocuSign or similar links) migrates as a URL field; the actual signed PDF does not migrate unless it is stored as an attachment. For customers moving to Salesforce CPQ, we flag Quote as a pre-migration scope item because CPQ uses a different quoting data model that should be designed before record migration.

Gold-Vision Service Desk Tickets support custom fields, conversation threads, and agent assignment. They map directly to Salesforce Case. Gold-Vision ticket status values remap to Salesforce Case Status, priority migrates to Priority, and conversation history migrates as EmailMessage records linked to the Case. If the destination Salesforce org does not include Service Cloud, we flag this during scoping because Cases require a Service Cloud license in a Sales-only org.

Gold-Vision User records carry role, team, and contact details. Owner assignment on records references the User ID. We map Gold-Vision users to Salesforce Users by email match. Any Gold-Vision User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on most standard objects. Active/inactive status in Gold-Vision maps to the Active flag in Salesforce.

Documents and file attachments stored against Accounts, Contacts, Opportunities, Projects, and Tickets in Gold-Vision export as binary blobs. We re-associate them to the correct Salesforce record via ContentDocumentLink using the Gold-Vision record's cross-reference ID (gv_account_id__c, gv_contact_id__c, etc.). Files over 25 MB require chunked ContentVersion upload through the Salesforce Bulk API. We flag oversized files during the scoping audit so that the customer can decide whether to migrate them or leave them in Gold-Vision's document store.

Gold-Vision uses tags and categories as organisational labels across objects. We preserve the full tag and category taxonomy and re-apply labels to migrated records. Tags stored as multi-checkbox properties migrate to Salesforce multi-select picklist fields on the relevant object (contact_tags__c, account_categories__c, etc.). Tags used for content or campaign classification migrate to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping based on whether they use Salesforce Topics elsewhere.

Emails, calls, and appointments synced from M365 and Outlook are logged as Communications against the relevant Contact or Account in Gold-Vision. We export the full communication log with timestamps, direction (inbound/outbound), and body content. Emails migrate to Salesforce EmailMessage records linked to Tasks; calls migrate to Task with TaskSubtype=Call and CallDurationInSeconds; meetings migrate to Event with StartDateTime and EndDateTime preserved. We use the Salesforce Bulk API 2.0 for this phase because communication log volume typically exceeds what the standard REST API can handle in a single migration window.

Gold-Vision supports unlimited additional fields on all major objects via its API. We extract the full custom field schema per object during scoping and map each to a corresponding Salesforce custom property. Field type mapping follows the dominant type: text fields map to Text(255), dates to Date, numbers to Number, and picklists to Picklist. Gold-Vision's dynamic screen designer means field names and layouts vary per tenant, so we capture the complete per-tenant schema rather than relying on a generic template. Custom field migration happens after the standard field mapping is validated in Sandbox.