Migrate from ContactWise CRM to Twenty CRM

ContactWise Contacts map to Twenty's Person object, which stores name, email, phone, and address fields. We perform a standard field-to-field mapping on standard fields and identify every ContactWise custom property during scoping. Twenty uses workspace-level field definitions, so we create each custom field in Twenty before importing any Person records. Custom property data types are mapped to Twenty field types (text, number, date, single-select, multi-select, URL, currency). Multi-select picklists in ContactWise convert to Twenty multi-select fields.

ContactWise Company records map to Twenty's Company object. The company name, domain, industry, employee count, and address fields map directly. Custom company properties are handled the same way as custom Contact properties: we create the matching Twenty field before import, then load the data. Companies must be imported before Persons so that the Person-to-Company relationship (linked via the Person's company field) is satisfied at insert time.

ContactWise Leads are a distinct object from Contacts with their own status and source attribution fields. We import them as Twenty Persons with a custom lead_status field preserved from the source. If the customer prefers a dedicated Lead object in Twenty, we create a custom Lead object with the relevant fields and import into that instead; the customer decides during scoping. The original lead source attribution migrates as a custom field.

ContactWise Opportunities map directly to Twenty's Opportunity object. Opportunity name, amount, stage, expected close date, and owner assignment migrate directly. Pipeline stage values from ContactWise are mapped to Twenty's Opportunity stage definitions, which we configure before import. If ContactWise uses multiple deal pipelines, we create corresponding Opportunity status columns in Twenty.

ContactWise pipeline stage definitions (stage names and order) are documented during discovery and recreated in Twenty as Opportunity stage columns. Each stage's probability percentage migrates from ContactWise to Twenty's stage probability field. If the customer uses multiple pipelines in ContactWise, we map each to a separate set of stage columns in Twenty.

ContactWise Workflow definitions are stored as platform configuration, not as data records with an exportable API. We audit every active workflow during discovery, document the trigger type, conditions, and actions for each rule, and deliver a written workflow inventory to the customer's admin. The admin rebuilds the logic in the destination platform. Time-based triggers, process reminders, and conditional routing that have no direct Twenty equivalent are flagged explicitly.

ContactWise tickets do not map to a single Twenty object. We split each ticket into a Twenty Activity record (containing the ticket subject, description, status, priority, and original ticket ID as a reference field) and a linked Task record for any action items assigned to team members. The ticket-to-contact association is preserved by linking the Activity to the Person record that owns the original ticket. Ticket comments and conversation history migrate as Activity comments.

ContactWise Time Entries are linked to Contacts, Tickets, or Projects but do not map directly to a standard Twenty object. We create a custom TimeEntry object in Twenty with fields for duration, date, billable flag, description, and linked Person. We map the source Time Entry duration and date fields directly and link to the Person record that the time was logged against. Projects (if used in ContactWise) are recreated as Twenty Companies with a project-type tag or a custom field.

ContactWise documents and attachments associated with Contacts, Opportunities, or Tickets are exported to cloud storage (customer-provided bucket) and linked to the corresponding Twenty record (Person, Opportunity, or Activity) via a URL field or as a Note attachment. We handle file metadata (filename, file type, upload date) during export. Large binary attachments may require chunking and are validated for size limits during scoping.

ContactWise Owners referenced on Contact, Company, and Opportunity records are matched to Twenty Workspace Users by email address. We extract every distinct owner referenced in the export and create a user mapping table. If a ContactWise Owner does not have a corresponding Twenty User at migration time, the record is held in a reconciliation queue and the original owner reference is preserved in a custom field until the admin provisions the user.