Migrate from Gold-Vision to Nutshell

Gold-Vision Accounts map directly to Nutshell Accounts. We use the Gold-Vision account name as the Account name field and the primary address block as the billing/shipping address in Nutshell. AccountId on all child records is resolved at import time so that the parent Account exists before any Contact or Opportunity insert. Industry, annual revenue, and phone fields migrate as standard fields; any additional Gold-Vision custom account fields migrate to Nutshell custom fields on the Account object.

Gold-Vision Contacts link to Accounts via the parent Account relationship and carry email, phone, communication history, and unlimited custom fields. We preserve the Account-Contact linkage by resolving AccountId during import. Nutshell's People object receives the full contact record including name fields, email address, phone numbers, and any Gold-Vision custom contact fields as typed Nutshell custom properties. Tags from Gold-Vision migrate to Nutshell's tag field on the People record.

Gold-Vision Leads are a distinct record type with their own pipeline and status fields. We map Gold-Vision Lead status values to Nutshell Lead status values during the transform step. Lead_Source and any Gold-Vision lead custom fields migrate to Nutshell custom fields on the Lead object. If the Gold-Vision Lead has been attached to a Campaign, we preserve that association via a Nutshell tag on the Lead record for segmentation by the customer's admin post-migration.

Gold-Vision Opportunities sit inside named Pipelines with configurable Stages, probability weights, close dates, and monetary values. We map Opportunities to Nutshell Opportunities with the stage sequence and probability percentages preserved. The AccountId reference is resolved via the parent Account name lookup. Custom opportunity fields from Gold-Vision migrate to Nutshell custom fields on the Opportunity object. We configure the Nutshell pipeline stages to match the Gold-Vision stage naming and sequence during the schema preparation step.

Gold-Vision allows multiple named pipelines. We capture the full pipeline structure including stage names, probabilities, and stage order. In Nutshell, each pipeline becomes a named Pipeline with Stage values that we configure to match the Gold-Vision stage sequence. Probability percentages are rounded to integers as Nutshell requires. The mapping is stored in the migration schema document so the customer can validate the stage alignment before the production migration.

Gold-Vision Projects are standalone records with time entries and task hierarchies that have no direct equivalent in Nutshell's object model. We export each Project record with its name, description, assigned Account reference, project status, and any custom fields. In Nutshell, we create a project_reference__c custom text field on the Account object and populate it with the Gold-Vision Project name and a status indicator. Time entries associated with Projects are exported as Tasks with a project tag and are linked to the related Account. Customers should validate during scoping whether the project reference approach meets their operational needs or whether project records need to live in a separate project management tool post-migration.

Gold-Vision Service Desk Tickets support custom fields, conversation threads, and agent assignment with open/closed status and priority. Nutshell does not have a native service desk object. We export the full ticket record and map it to a Note attached to the relevant Account, with the ticket ID and status preserved in the note body. For organisations that actively use Gold-Vision's service desk, we recommend creating a dedicated service_ticket_status__c custom field on the Account during schema preparation and using that as a lightweight ticket tracker, or evaluating a dedicated helpdesk integration post-migration.

Gold-Vision Communications (emails, calls, and appointments synced from M365, Outlook, and Gmail) log against the relevant Contact or Account with timestamps, direction, and body content. We export the full communication log and map it to Nutshell Tasks with the original timestamp preserved as ActivityDate. Call logs include duration and disposition in the Task description. Emails migrate as Tasks with the email body and subject line stored in the Task notes field. The WhoId (Contact or Lead reference) and AccountId are resolved at migration time via the email address lookup table built during the Contacts phase.

Gold-Vision Quotes carry line items, branding templates, and optional e-sign links. Nutshell does not have a native Quotes object. We export the quote header, line items, and status as a structured Note attached to the related Opportunity. E-sign metadata (such as DocuSign envelope URLs) is preserved as a text reference within the note. If the customer requires a native quoting tool post-migration, we recommend evaluating Nutshell's paid Advanced Plan quoting features or a third-party CPQ integration.

Gold-Vision supports unlimited additional fields on all major objects via its API. We extract the full custom field schema per object during the discovery phase and create matching custom fields in Nutshell during schema preparation. The Gold-Vision custom field API name is preserved as the Nutshell custom field label with the field type mapped to the closest Nutshell-supported type (text, number, date, dropdown, checkbox). Multi-select picklists in Gold-Vision map to Nutshell's tag field or a multi-value text field depending on the target object.