Migrate from VAIL-CRM to Twenty CRM

VAIL-CRM Contacts compile customer data from website interactions, telephone, email, live chat, and social media channels. We map standard fields (name, email, phone) directly to Twenty's People object. Due to Twenty's minimal standard field set, we pre-create industry-standard fields (jobTitle, department, website, source, contactType) in Twenty Settings before CSV import, per Twenty's documentation requirement that fields must exist before import. Multi-channel source identifiers (social media handles, chat IDs) map to custom fields on People.

VAIL-CRM Company records store organizational data linked to multiple contacts. We preserve the contact-company relationship by matching on company name or external ID where available. Twenty's Company object requires pre-creation of standard fields like industry, employeeCount, annualRevenue, and website before import, per the known field-gap gotcha documented in Twenty's GitHub issue #13953. We create these fields during the schema preparation phase.

VAIL-CRM Deals track sales opportunities with associated monetary values, stage assignments, and close dates. Pipeline stage names vary by VAIL-CRM instance and require mapping to Twenty's Opportunity pipeline stages. Stage probability weights migrate as configuration on the pipeline. Closed-Won and Closed-Lost reasons from VAIL-CRM custom properties map to Twenty Opportunity custom fields.

VAIL-CRM custom pipeline configurations and stage sequences differ between instances. We extract the full pipeline definition including stage order, names, and probability weights from the source instance during discovery. Twenty requires pipeline configuration before Opportunity import. We create the pipeline and stages in Twenty's Settings Data Model section before migrating Opportunity records.

VAIL-CRM activity history across communication channels (web, phone, email, live chat, social) may be stored across multiple object types depending on which channels are integrated. We map call engagements to Twenty Task with TaskSubtype=Call, email to Task with email-related fields, meetings to Event, and standalone notes to Note. Activity timestamps are preserved as ActivityDate for timeline ordering. The multi-channel compilation in VAIL-CRM requires deduplication during export to avoid duplicate activity records in Twenty.

VAIL-CRM's marketing automation component stores campaign records and workflow logic. Marketing workflows do not migrate as code. We export campaign metadata (name, status, start/end dates, target audience criteria) as a written inventory. Campaign target audience criteria require manual rebuild in Twenty or a separate marketing automation tool. If the customer uses Twenty for campaign tracking only, we migrate campaign records as a custom object with linked Opportunities.

VAIL-CRM's service automation component stores support tickets and customer service interactions with status and assignment data. Ticket records migrate to a Twenty custom object (Ticket or Case) if the customer requires support case management. Custom ticket field configurations must be mapped individually during discovery. Service automation workflows do not migrate; we deliver a written inventory for manual rebuild in Twenty's workflow framework.

VAIL-CRM custom fields added to standard objects vary by implementation. We capture the full custom field schema including field type, required status, and picklist values during discovery. Custom fields must be pre-created in Twenty's Settings Data Model before any CSV import runs, per Twenty's import documentation. Field types map from VAIL-CRM to Twenty equivalents (text to string, number to number, date to date, picklist to select).

VAIL-CRM owner relationships (Contact owner, Deal owner) map to Twenty Workspace Members. Twenty's migration documentation explicitly requires inviting all team members before importing data that includes user references. We extract distinct owner email addresses from VAIL-CRM records, verify corresponding Twenty workspace members exist, and provision any missing members before migration resumes.

VAIL-CRM custom objects migrate to Twenty custom objects of equivalent name. We pre-create the destination schema in Twenty's Settings Data Model, including all custom fields, field types, and any lookup relationships to standard objects (People, Company, Opportunity). Twenty's v2.0 framework allows building apps on top of custom objects without forking the codebase, giving teams extension flexibility post-migration.