Migrate from Weave to Twenty CRM

Weave Contact records migrate as Twenty People objects. Each patient's primary company (practice or location) resolves to a companyId link pointing to the corresponding Company record. For patients without a linked location, FlitStack creates a standalone People record with either a placeholder company or a custom 'Unassigned' flag to preserve data integrity and ensure relationship consistency in Twenty's schema.

Weave stores first name and last name as separate contact properties. These two fields concatenate to populate the Twenty People name field. For contacts that lack a name in Weave, FlitStack preserves the original source identifier (such as an internal Weave ID) in a custom 'Source_Name__c' field on the People record to maintain traceability.

The primary email address from each Weave Contact maps directly to the Twenty People email field. When a Weave contact has multiple email addresses on file, the primary email populates the standard email field while additional addresses are stored in a custom multi-value field called 'Additional_Emails__c' using a semicolon-separated format.

Weave's primary phone field maps to the Twenty People.phone standard field. Mobile phone, home phone, and work phone stored as separate contact properties in Weave migrate to custom text fields on the People record (Mobile_Phone__c, Home_Phone__c, and Work_Phone__c respectively) to preserve all available contact numbers.

Weave stores address components (street, city, state, postal code, and country) as separate sub-fields on the contact record. These consolidate into a single formatted address string in Twenty's People.address field while maintaining individual custom fields for city, state, and postal code to enable precise filtering, segmentation, and geographic reporting.

Weave tracks SMS opt-in, email opt-in, and call preferences as per-contact settings. Since Twenty has no native equivalent for these preference fields, FlitStack migrates each preference as a custom boolean field on the People record: SMS_Opt_In__c, Email_Opt_In__c, and Call_Permission__c, preserving the original consent status from Weave.

Weave Locations representing practices, clinics, or offices map directly as Twenty Companies. Each Weave location name becomes a Company.name value. For multi-location practices in Weave that maintain separate contact lists and scheduling queues, FlitStack generates separate Company records linked by a custom 'Practice_Group__c' field to represent the parent organization.

Location address fields (street, city, state, postal code, country) from Weave map to Twenty Company address fields following the same transformation pattern applied to contact addresses. The consolidated address string populates the standard Company.address field while individual sub-fields (city, state, postal_code) are preserved as custom fields for reporting and geographic segmentation.

Weave's patient-to-location association (identifying which clinic or practice a patient belongs to) maps to People.companyId pointing to the corresponding Twenty Company record. When a patient has multiple associated locations in Weave, secondary location links are stored as a custom 'Additional_Locations__c' multi-select field on the People record.

Weave communication threads (SMS messages, VoIP calls, emails) transform into Twenty Tasks. Each Task captures the interaction direction (inbound/outbound), communication type (call/sms/email), call duration stored in a custom Duration_Seconds__c field, the original timestamp, and the original Weave thread ID. The task body stores a truncated transcript or summary for quick reference.

Weave appointments transform into a Note linked to People and Company records plus a companion Task. The Note contains appointment type, duration, and clinical notes while the Task carries the appointment date as dueDate and the assigned provider in the assignee field. Weave reminder sequences do not migrate — those must be rebuilt using Twenty's workflow builder on Pro or Organization tiers.

Weave's automated SMS and email appointment reminders built on Weave's automation engine have no equivalent in Twenty's workflow model. These workflows cannot be exported and must be rebuilt from scratch using Twenty's workflow builder (available on Pro and Organization Cloud tiers) or via an external scheduling integration. FlitStack exports reminder configurations as a JSON reference document for your Twenty admin to use during the rebuild.

Weave tasks and front-desk action items map directly to Twenty Tasks. Task status (completed/incomplete), due date, assignee, and description fields carry over directly from Weave. The completed flag preserves the original completion state so your team can review historical task data in Twenty without needing to re-create the work history.

Weave custom contact properties migrate as custom fields on the Twenty People object. Field type mapping follows these rules: text properties become TEXT fields, numeric properties become NUMBER fields, date properties become DATE fields, and picklist properties become SELECT or multi-select fields depending on Weave's configuration. All custom fields must be pre-created in Twenty Settings before import.

Weave custom location properties such as tax ID, NPI number, scheduling rules, and clinic-specific attributes migrate as custom fields on the Twenty Company object. The same type-mapping rules applied to People custom fields (text, number, date, picklist) apply here, ensuring data types remain consistent across both object types during migration.

Weave's integrated billing and payment records have no direct equivalent in Twenty's standard data model. FlitStack migrates billing summaries (most recent payment amount, date, and status) as Note records attached to the relevant People or Company record. Full payment history, invoice records, and outstanding balances require a custom object setup in Twenty available on Pro and Organization tiers.

Weave owner assignments identifying which staff member owns a contact or location resolve via email match to Twenty workspace members. Unmatched owners are flagged in a pre-migration report for manual assignment. Original ownership metadata is preserved in a custom 'Source_Owner__c' field on each record, storing the Weave owner email for audit and reference purposes.

Weave's HIPAA compliance infrastructure including audit logs and secure messaging has no native equivalent in Twenty's general-purpose CRM model. FlitStack preserves a HIPAA_Flag__c custom boolean field on People records and a 'Compliance_Notes__c' field for storing audit trail references from Weave's export. The compliance framework itself must be addressed at the deployment level.