Migrate from Gold-Vision to Pipedrive

Gold-Vision Accounts map directly to Pipedrive Organisations. The Account ID becomes the Organisation ID; Gold-Vision's industry, address, phone, and owner fields map to Organisation's equivalent typed fields. Account-Category labels from Gold-Vision migrate as Organisation custom fields. We use Organisation ID as the parent-reference key before any Person import because Pipedrive requires a linked Organisation for deal creation.

Gold-Vision Contacts map to Pipedrive People. We preserve the Account-Contact relationship by resolving Gold-Vision's account_id to the newly created Organisation ID during import. Email, phone, job title, and address fields map to People fields directly. Custom Contact fields from Gold-Vision's screen designer become People custom fields in Pipedrive, created before the Person import phase.

Gold-Vision Leads are a distinct record type with their own pipeline and status fields, which map to Pipedrive Leads. We preserve the Lead status, source, and score fields as custom fields in Pipedrive. If the customer converts Gold-Vision Leads to Contacts before migration, we treat them as People records; if Leads remain unqualified, they land in Pipedrive's Lead inbox for follow-up.

Gold-Vision Opportunities map to Pipedrive Deals. The Opportunity's pipeline and stage sequence becomes a Pipedrive Pipeline with Stages reconfigured to match Gold-Vision's stage names and probability weights. Deal value, close date, and owner assignment migrate directly. Gold-Vision's custom Opportunity fields become Deal custom fields.

Gold-Vision's named pipelines and stage sequences become Pipedrive Pipelines and Stages. We capture each Gold-Vision stage's name, probability percentage, and order, then configure Pipedrive Stages with matching probability values. If Gold-Vision has multiple pipelines, we create multiple Pipedrive Pipelines and map Deal records to the correct pipeline at import time using a pipeline_id field in the migration workbook.

Gold-Vision Projects are standalone records with time entries and task hierarchies not natively modelled in Pipedrive. We export Project as a Deal with a project_reference__c custom field holding the original Gold-Vision Project ID, a project_name__c field, and a project_status__c field. Time entries associated with the project migrate as Activity records linked to the Deal with type=Task and a note indicating the original time entry data. If the customer requires a more granular project model, we recommend a separate project management tool with a Pipedrive integration.

Gold-Vision Campaigns include multi-stage status tracking and ROI reporting, which have no direct Pipedrive equivalent. We export Campaign records and member associations as Activity records with a campaign_name__c label grouping. Campaign status migrates as a custom Activity field. For ongoing campaign tracking, we recommend Pipedrive's Target tool or a dedicated marketing platform with Pipedrive integration post-migration.

Gold-Vision Quotes carry line items, branding templates, and optional e-sign links. Pipedrive does not have a native Quote object on Essential and Advanced tiers. We export Quote headers and line items as a Deal custom summary field (quote_summary__c) in plain text, and the quote PDF as a Deal attachment. If Pipedrive's sell-as-you-go Quote tool (Professional and above) is available in the customer's tier, we map Quote line items to Products linked to the Deal.

Gold-Vision Tickets are service desk records with conversation threads and agent assignment. Pipedrive does not have a native service ticket object. We export Tickets as Activity records with type=Task, a ticket_reference__c custom field, and conversation threads as Activity notes. If the customer requires ongoing ticket management, we recommend Pipedrive's native service add-on or a dedicated helpdesk integration post-migration.

Gold-Vision's dynamic screen designer means field names and available fields can vary per tenant. We extract the full custom field schema per object during discovery and create matching Pipedrive custom fields before any data import. Field types are mapped: text to varchar, number to int/float, date to date, picklist to picklist, multi-select to multi-select. Gold-Vision's per-tenant field variations are consolidated into the global Pipedrive custom field definition for the account.

Gold-Vision Communication Logs (emails, calls, appointments synced from M365 and Outlook) map to Pipedrive Activities. Email content migrates as an Activity with type=Email and the email body preserved in the note. Calls migrate as Activity with type=Call and duration field. Meetings and appointments migrate as Activity with type=Meeting. Timestamps, direction, and participants are preserved in custom Activity fields.

Gold-Vision document attachments on Accounts, Contacts, Opportunities, Projects, and Tickets migrate as Pipedrive Deal or Organisation attachments. We extract binary blobs, upload to Pipedrive's file storage, and link via the attachment API. E-sign documents from Gold-Vision Quotes preserve the URL reference as a custom field; the actual signed PDF is migrated as a file attachment where supported.