Migrate from Wice CRM to Twenty CRM

Wice Organizations map to Twenty Company records. Wice enforces a contact-to-organization relationship, so we export Organizations first and use the Wice organization ID as a reference key when importing Contacts. The Wice organization name maps to Company.displayName; industry maps to Company.industry; address fields map to Company.address fields. Organization is the parent in the relationship hierarchy, so it must be imported before any Contacts that reference it.

Wice Contacts map to Twenty Person records. We resolve the organization linkage by looking up the target Company ID using the Wice organization foreign key before writing each Person record. Name, email, phone, and address fields map directly. Custom fields on Wice Contacts (Gold tier) are pre-created as custom fields on the Twenty Person object via the metadata API before import begins.

Wice Deals map to Twenty Opportunity records. The deal value, expected close date, and owner assignment transfer directly. Pipeline stage names are captured from the customer's live Wice installation during discovery because stages are fully customizable per Wice installation. We create a matching Opportunity stage name set in Twenty via the GraphQL API before migration and generate a stage-mapping table showing each Wice stage and its Twenty equivalent before any Deal records are written.

Wice allows unrestricted customization of pipeline stage names. A deal in stage 'Angebot gesendet' (Proposal Sent) in a German Wice installation maps to a Twenty stage name the customer defines during scoping. We capture the actual stage list from Wice during discovery, propose a canonical English stage name set for Twenty, and apply it via the Twenty settings API. Stage probability percentages map to Twenty's stage probability field per stage name.

Wice Projects do not have a direct Twenty standard object equivalent. We create a Project custom object in Twenty via the metadata API with custom fields for project name, status, start date, end date, and description. Project-task hierarchy is preserved by creating the Project record first and then linking child Task records via a lookup relationship field that we add to the Project custom object.

Wice Tasks exist both inside Projects and as standalone records linked to Contacts or Deals. We export both contexts and reconstruct the hierarchy in Twenty. Project-bound tasks reference the target custom Project record via the lookup field. Standalone tasks link to the appropriate Person, Company, or Opportunity record. Status, priority, assignee, and due date transfer directly; completed date maps to Twenty's completedAt field if populated.

Wice differentiates basic and advanced campaigns with different property sets. Both tiers map to a Campaign custom object we create in Twenty. Advanced campaign targeting properties and tracking fields become custom fields on the Campaign object. Campaign history data (sent, open, click counts) may be partial because Wice stores some campaign analytics internally and not in the exportable record fields. We flag any campaign fields that are empty post-export and document them as data-gaps for the customer's review.

Wice Tickets map to a Ticket custom object in Twenty. We create the Ticket custom object via the metadata API with fields for ticket number (Wice generates sequential IDs), status, priority, subject, and description. Linked contacts and organizations map to Person and Company lookups. Custom ticket fields from Wice Gold tier are pre-created as custom fields on the Twenty Ticket object before migration.

Wice free-text Notes attached to contacts, organizations, deals, and projects migrate to Twenty Note records linked via ContentDocumentLink to the parent Person, Company, Opportunity, or custom object record. Note body transfers as plain text; Wice formatting (bold, lists) is simplified to plain text because Twenty Note does not support rich text in the current release. We preserve the source-object linkage by recording the original Wice object type and ID in a migration reference field.

Wice Gold tier custom fields on contacts, organizations, deals, projects, and tickets are exported as additional columns in the CSV. Before migration, we create matching custom fields on the corresponding Twenty objects (Person, Company, Opportunity, Project, Ticket) via the Twenty metadata API. Picklist-style custom fields in Wice require explicit value mapping if the destination Twenty picklist options differ. Fields are created before any data import because CSV import creates records, not fields.

Wice Owner references on contacts, organizations, deals, and tasks map to Twenty WorkspaceMember records. We extract distinct owner values during discovery and match by email against the target Twenty workspace. Any Wice owner without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer to provision before record import. Migration cannot proceed past Deal import until all Owner references are resolved because OwnerId is required on Opportunity.

Wice uses a category system for deduplication and classification that does not map 1:1 to any Twenty native feature. We export category assignments as a comma-separated text value stored on the migrated record. During scoping, the customer chooses whether to keep category values as plain text fields, map them to Twenty's topic feature, or treat them as a data hygiene exercise and leave categories behind.