Migrate from Gold-Vision to Microsoft Dynamics 365 Sales

Gold-Vision Accounts map directly to Microsoft Dynamics 365 Account. Gold-Vision's unlimited custom fields on Account transfer to custom attributes on the Account entity in Dataverse, with type mapping performed during discovery (text fields become nvarchar, numeric fields become decimal or integer, date fields become datetime2). The Gold-Vision Account ID is preserved in a custom field gv_account_id__c for post-migration reconciliation and ID cross-referencing.

Gold-Vision Contacts map to Dynamics 365 Contact, preserving the link to the parent Account via the accountid lookup. Gold-Vision's unlimited Contact custom fields transfer to Dataverse Contact custom attributes. We maintain the Gold-Vision Contact ID in gv_contact_id__c and map Gold-Vision's Tags and Categories to Dynamics 365 multi-select picklist fields or to Topics with TopicAssignment records depending on usage pattern.

Gold-Vision Leads map to Dynamics 365 Lead. Lead status fields (leadscore, leadstatus, source campaign) transfer to their Dynamics 365 equivalents. Gold-Vision Lead custom fields preserve on the Lead entity. If the customer uses Gold-Vision's lead qualification workflow, the qualification outcome maps to the Lead Status field. Active Leads are imported before Contact conversion runs so that the system of record is consistent at cutover.

Gold-Vision Opportunities map to Dynamics 365 Opportunity with pipeline stages translated to Dynamics 365 StageName values and probability weights mapped to StageProbability. The Gold-Vision pipeline sequence is captured during discovery and translated into a Microsoft Dynamics 365 Sales Process that whitelists the relevant stage values. Close date, estimated value, and weighted forecast migrate directly. Closed-won and closed-lost reasons map to custom Opportunity fields if required by the customer's forecasting model.

Gold-Vision's named pipelines map to Dynamics 365 Record Types on Opportunity, each with its own Sales Process and Page Layout. Stage sequences and names from Gold-Vision are reproduced in the Microsoft Dynamics 365 Sales Process editor during the schema-design phase before any data moves. Probability percentages round to the nearest integer as Dynamics 365 requires.

Gold-Vision Campaigns map to Dynamics 365 Campaign, preserving campaign type, target audience, and ROI tracking fields. Campaign member associations from Gold-Vision migrate as CampaignMember records linked to the relevant Leads and Contacts. Gold-Vision's multi-stage campaign status (Draft, Active, Completed) maps to Dynamics 365 Dynamics355Sales_Campaign_Status values.

Gold-Vision Quotes migrate to Dynamics 365 Quote, with QuoteLineItem migrating after the parent Quote, Product2, and Pricebook2 records are in place. Quote header fields (quotenumber, customer, expiration, terms) map directly. E-sign document URLs stored in Gold-Vision are preserved as a URL field on the Quote; the signed document itself is exported as a SharePoint or Dataverse file attachment and re-linked post-migration. Quote template customisations do not migrate; we document the template structure for rebuild in Dynamics 365's document template editor.

Gold-Vision Projects are standalone records with time entries, task hierarchies, and assigned Contacts that do not exist as a native entity in Microsoft Dynamics 365 Sales . We export Projects as Opportunities, creating a custom field gv_project_id__c for cross-reference and custom fields for project-specific metadata (project manager, start date, estimated hours, status). The linked time entries become custom Activity records attached to the re-modelled Opportunity. Customers requiring a native project model should evaluate Dynamics 365 Project Operations as a separate add-on; we do not configure that within the CRM migration scope.

Gold-Vision Tickets migrate to Dynamics 365 Case, which requires the customer to hold a Service Cloud licence on top of their Sales Professional or Enterprise licence. Gold-Vision ticket priority, status, and conversation threads map to Case Priority, Status, and EmailMessage records attached to the Case. We flag any customer without an active Service Cloud licence during scoping so that Case migration can be scheduled post-licensing rather than blocking the core CRM migration.

Gold-Vision Communications logs synced from M365, Outlook, and Gmail become Dynamics 365 Activity records. Email content loads as EmailMessage linked to the Contact or Account WhoId; calls become Task with TaskSubtype=Call; appointments become Event with start and end times preserved. The Gold-Vision communication log carries Gold-Vision internal record IDs that we resolve to Microsoft Entra ID user lookups and Contact/Account references in Dataverse before loading. This ID resolution step is the most migration-specific part of the engagement and requires a mapping table built during discovery.

Gold-Vision's unlimited custom fields per object transfer to Dataverse custom attributes. We audit the total custom field count per entity during discovery because Dynamics 365 has entity-level field limits (approximately 800 for standard entities, 500 for custom entities). Gold-Vision tenants with heavy custom field usage may require schema cleanup or tier upgrade to accommodate the full field set in Dynamics 365.

Gold-Vision file attachments stored against Accounts, Contacts, Opportunities, Projects, and Tickets are exported as binary blobs and re-associated to the correct Dataverse record via SharePoint Document Locations (if the customer's Dynamics 365 org uses SharePoint for document management) or as Note records with file attachments. We configure the SharePoint or Dataverse file storage during migration setup if not already present. Attachments stored in Gold-Vision's document management module map to SharePoint libraries for the corresponding entity.

Gold-Vision Users map to Dynamics 365 Users resolved by email address. The Gold-Vision user role and team structure is translated into Dynamics 365 Security Roles and Teams during the schema-design phase. Any Gold-Vision User without a matching Microsoft 365/Azure AD account is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references on Opportunities and Cases must resolve to a valid Dynamics 365 User.