Migrate from Visual Practice to Twenty CRM

Visual Practice contact records map directly to Twenty's People object. Every standard contact field — name, email, phone, job title — maps to its Twenty equivalent. Primary company association requires a Company record to exist in Twenty first; we sequence Company import before People import to satisfy the companyId foreign key.

Visual Practice company records map 1:1 to Twenty's Companies object. Company name, domain, industry, employee count, and address fields migrate as direct mappings. If Visual Practice stores a parent-company relationship, we map it to Twenty's parentCompanyId relation — circular references are flagged before migration.

Visual Practice deals migrate as Twenty Opportunities with deal name mapped to name, amount mapped to amount, close date mapped to closeDate, and stage mapped to stage. Stage values are written as pick-list strings; we recommend pre-defining stage values in your Twenty workspace before migration to avoid import errors on undefined pick-list values.

Visual Practice call and email records map to Twenty Tasks with Type set to 'Call' or 'Email' and the original description preserved. Meeting records with start and end times map to Tasks with the time range stored in the description or a custom datetime pair. Rich-text meeting notes migrate to Twenty Notes attached to the relevant People or Opportunity record.

Visual Practice notes migrate as Twenty Notes. We preserve the original create timestamp and author by storing them in custom fields on the Note record since Twenty's native createdAt is set at import time. Notes are linked to their parent People, Companies, or Opportunities records using Twenty's relation field system.

Visual Practice task records map directly to Twenty Tasks. Title maps to title, due date maps to dueAt, completion status maps to completedAt (null if incomplete), and assignee is resolved by email match against Twenty workspace members. Unmatched assignees are flagged before migration for manual assignment.

Visual Practice owner IDs are resolved against Twenty workspace members by email address. Every People, Company, Opportunity, and Task record receives an OwnerId pointing to the matched WorkspaceMember. If a Visual Practice owner has no corresponding Twenty user, the record is assigned to a fallback workspace member and the orphan is logged for admin review.

Visual Practice custom objects migrate to Twenty's custom object framework. Custom object definitions (field names, field types) are read from Visual Practice's schema export and recreated in Twenty's data model UI or via API. Custom object relationships that use N:N associations in Visual Practice require junction objects in Twenty — we surface this mapping in the migration plan.

File attachments from Visual Practice are downloaded and re-uploaded to Twenty's file storage. We preserve the original filename, file type, and upload timestamp. Files attached to People, Companies, or Opportunities are linked to their destination record in Twenty. Size limits apply — files exceeding Twenty's storage constraints are flagged for alternative storage.

Visual Practice pipeline stages map to Twenty Opportunity stage pick-list values. Each stage name is written as a string value in Twenty's stage field. Probability values associated with each stage are stored in a custom field since Twenty's base Opportunity model does not have a native probability field. Stage ordering is preserved as defined in the Visual Practice pipeline configuration.