Migrate from Gold-Vision to Twenty CRM

Gold-Vision Account records map directly to Twenty CRM Organization records. Gold-Vision account fields (address, industry, annual revenue, owner) map to the corresponding Twenty Organization fields. The Organization is the parent record for all Person records, so it must be imported before any Contact migration. Gold-Vision's multi-business entity configuration maps to multiple Twenty workspaces or a single workspace with filtered views per entity.

Gold-Vision Contact records map to Twenty CRM Person records. Each Person links to an Organization via a foreign key resolved at migration time. Gold-Vision's email, phone, job title, and communication history fields map to the corresponding Twenty Person fields. Custom fields on Contact migrate as Twenty custom fields on the Person object.

Gold-Vision Leads are a distinct record type with their own pipeline and status fields. Twenty CRM does not have a separate Lead object; all people records are Person records. We import Gold-Vision Leads as Persons with a custom field gv_lead_source__c carrying the original Lead status and source, or as Opportunities in the early pipeline stage if the customer prefers a pipeline-based qualification model. The approach is chosen during scoping based on the customer's qualification workflow.

Gold-Vision Opportunity records map to Twenty CRM Opportunity records. The pipeline stage from Gold-Vision maps to Twenty's pipeline stage, and close dates, monetary values, and probability weights transfer directly. Gold-Vision custom opportunity fields migrate as Twenty custom fields on the Opportunity object.

Gold-Vision's named pipelines with configurable stages map to Twenty's Pipeline and Stage configuration. We capture the full stage sequence, probability percentages, and stage names during discovery and configure the equivalent pipeline structure in Twenty before migration. Multiple Gold-Vision pipelines map to multiple Twenty pipelines or a single pipeline with a type field if the customer prefers consolidated views.

Gold-Vision Projects are standalone records with time entries, task hierarchies, and assigned contacts that do not have a direct Twenty CRM equivalent. We export Projects as a custom record type in Twenty (Project__c) with fields for project name, dates, status, and assigned contacts, or as Opportunities with a project_type__c flag if the customer prefers a pipeline-based view. Time entries migrate as Activity records with a project reference field. Customers should validate that the chosen representation meets their operational needs before migration.

Gold-Vision Campaign records with multi-stage status tracking and ROI reporting do not have a native Twenty CRM equivalent. We export campaign records and member associations and map them to Twenty as a custom Campaign__c object with a CampaignMember__c junction object linking to Person records. The customer decides whether to build a campaign reporting view in Twenty or use an external marketing analytics tool.

Gold-Vision Quotes carry line items, branding templates, and e-sign links. Twenty CRM does not have a native Quote object. We export quote headers and line items as OpportunityLineItem records attached to the parent Opportunity, or preserve them as an external document reference with the quote URL carried in a custom field. E-sign metadata preserves as a URL reference; the actual signed document does not migrate as a native object.

Gold-Vision service desk Tickets support custom fields, conversation threads, and agent assignment. Twenty CRM does not have a native service desk object. We map Tickets to a Twenty service pipeline (an Opportunity with RecordType=Service) and conversation threads to Activity records linked to the Opportunity. Alternatively, customers who need a dedicated service workflow use a custom Ticket__c object.

Gold-Vision supports unlimited additional fields on all major objects via its API. We extract the full custom field schema per object during discovery and pre-create the equivalent custom fields in Twenty CRM through Settings → Data Model before any data migration. Field types are mapped from Gold-Vision's data types to Twenty's supported field types (text, number, date, select, multi-select, checkbox, currency, URL).

Gold-Vision documents and file attachments stored against Accounts, Contacts, Opportunities, Projects, and Tickets migrate as binary blobs re-associated to the correct record in Twenty CRM. Twenty supports file attachments on Organizations, Persons, and Opportunities. Large attachments (>25 MB) may require chunked upload handling. We preserve the original filename and attachment context during migration.

Gold-Vision uses tags and categories as organizational labels across objects. We preserve the full tag and category taxonomy and re-apply labels to migrated records in Twenty CRM. Tags migrate as a tagging solution implemented in Twenty (custom tag field or external tagging tool), as Twenty does not have a native tagging system in the core product.