Migrate from Wired Plus to Twenty CRM

Wired Plus Contacts map directly to Twenty CRM Person records. The contact's email, name, phone, and address fields migrate as standard Person fields. We explicitly query and preserve the opt_in consent flag from Wired Plus as a custom boolean field or topic on the Person record to maintain GDPR compliance and prevent unconsented re-import. Lifecycle stage from Wired Plus (subscriber, lead, customer) migrates to a custom select field or topic tag for segmentation continuity.

Wired Plus Company records map to Twenty CRM Company. The company name, domain, address, and industry fields migrate as standard Company fields. We use the domain field as the dedupe key during import to prevent duplicate Company records for contacts sharing the same organization. Company must be created before Person records that reference it so that the lookup relationship is satisfied at insert time.

Wired Plus Deals map to Twenty CRM Opportunity. The deal name, amount, expected close date, and pipeline stage migrate as standard Opportunity fields. We resolve the Person (contact) and Company lookups at migration time using email and domain matching. Closed-won and closed-lost reasons from Wired Plus custom fields migrate as custom text fields on the Opportunity.

Wired Plus pipeline stages are defined per account. We extract the full stage sequence including stage names, order, and probability values during scoping. Each stage maps to a Twenty Opportunity stage with the corresponding position and probability percentage. Stages that have no equivalent in Twenty's default stage set are created as custom stage values before migration.

Wired Plus campaign records containing send history, open rates, click data, and performance metrics do not have a direct Twenty CRM equivalent because Twenty does not include native email campaign management. We map campaign name and status to Twenty Tasks or a custom Campaign object depending on the customer's reporting requirements. Campaign performance metrics (open rate, click rate) migrate as custom number fields on the custom object. The customer's team implements email campaign tooling separately or via Zapier-connected tools post-migration.

Wired Plus custom fields are account-specific and stored with field labels rather than internal field IDs in exports. We resolve field labels to internal identifiers during scoping by querying the Wired Plus field schema via API. Each custom field maps to a Twenty CRM custom field of matching type (text, number, date, select) that we pre-create in Twenty via the /metadata API before the first import. Picklist values from Wired Plus custom select fields migrate as select options on the corresponding Twenty custom field.

Wired Plus tags are flat string labels applied to contacts and companies. We export all tag assignments and reapply them as Twenty Tags (if enabled in the workspace) or as topic assignments on Person and Company records. Tag strategy is chosen during scoping: flat tag migration for contact segmentation or topic-based grouping for taxonomy alignment.

Wired Plus automation workflows define trigger-action sequences with conditional branches and time delays. We export workflow definitions as structured JSON metadata. The trigger event IDs, delay values, and condition logic require manual reconfiguration in Twenty's workflow builder because automation logic does not transfer between platforms. We deliver a written workflow audit log listing every active workflow with its trigger, conditions, actions, and recommended Twenty workflow equivalent for the customer's admin to rebuild.

Wired Plus landing pages store HTML content and form configurations. We export page HTML, asset URLs, and form field definitions. Pages with embedded forms require reconnection to a new form handler at the destination. We provide a landing page inventory document listing every page, its form fields, and the recommended rebuild path in Twenty or a connected form tool.

Wired Plus forms capture subscriber data and link to campaigns or landing pages. We export form field names and submission logs. Form-to-field mappings must be rebuilt at the destination because form handler IDs and webhook endpoints do not transfer. We deliver a form inventory with field mappings to guide reconstruction in Twenty or a third-party form tool.