Migrate from Visionary to Twenty CRM

Visionary contacts map to Twenty People records. The name field splits into firstName and lastName. Email, phone, job title, and address fields map to their Twenty equivalents. We preserve the Visionary contact ID in a custom field (source_id__c) for traceability and delta-run de-duplication.

Visionary company records map to Twenty Companies. Company name, domain, industry, employee count, and annual revenue fields map directly. Twenty's domain field is used for company website. Parent-company relationships in Visionary map to Twenty's relation fields if hierarchical structure exists.

Visionary deals map to Twenty Opportunities. Deal name becomes opportunity name, amount maps directly, stage maps via value mapping since stage names differ between platforms, and close date maps to expectedCloseDate. The linked companyId is resolved against the Companies import batch.

Visionary pipeline stage names do not match Twenty's default stage set. We map Visionary stage values to Twenty Opportunity stage values by your specified target pipeline. Stage-entered timestamps are preserved as custom datetime fields in Twenty since Twenty does not natively track stage-transition timestamps.

Visionary logged calls, emails, and meeting activities map to Twenty Tasks. Task type (call, email, meeting) maps to Twenty's type field. Subject, body, and original timestamps are preserved. Tasks are linked to their parent People or Opportunities record via Twenty's relation fields.

Visionary notes map to Twenty Notes. Rich-text formatting is preserved where possible. Notes are linked to their parent record (People, Companies, or Opportunities) via Twenty's relation fields during import. Author and create date are preserved as metadata on the Note record.

Visionary owner assignments on contacts, companies, and deals map to Twenty Workspace Members. We resolve by email match — Visionary owner email links to a Twenty user by email. Unmatched owners are flagged before migration; you either invite them to Twenty or assign their records to a fallback member.

Visionary custom objects map to Twenty custom objects. If Visionary supports custom objects, we map them 1:1 to Twenty's custom object model. Custom-object relationships that use N:N linking in Visionary may need Twenty junction objects — we surface this in the migration plan before execution.

Visionary file attachments are downloaded from Visionary and re-uploaded as Twenty Files attached to their parent records. File size limits follow Twenty's import constraints and vary by plan tier. Inline images embedded in Visionary notes are extracted and rehosted as Twenty Files where the import format allows, ensuring images display correctly after migration.

If Visionary tracks lead status as a separate field from lifecycle stage, we map it to a custom field on Twenty People. Twenty has no native lead-status concept — Twenty People records do not include a built-in lead-status field. The field is preserved as a custom pick-list field for reporting continuity and can be used in Twenty filters and views.