Migrate from WayMore to Twenty CRM

WayMore Contact records export via CSV from the dashboard contacts section and map to Twenty People. Core fields (name, email, phone, address) transfer directly. Behavioral data stored as custom properties on the Contact (e.g., last visited page, lead score, acquisition channel) map to Twenty custom fields that we pre-create in the Data Model before import. We preserve any opt-out or suppression status from WayMore as a boolean custom field in Twenty. WayMore's email subscription preferences migrate to the Twenty People emailOptOut field for compliance.

WayMore Company records map to Twenty Company records. The Company domain from WayMore becomes the Company website field. We create the Company record before importing any People that reference it so that the workspace-company link resolves at import time. If a WayMore Contact has no associated Company, it migrates as a standalone Twenty People record.

WayMore Deal records map to Twenty Opportunity records. The deal amount, stage, close date, and associated contacts migrate directly. WayMore's deal pipeline names map to Twenty Opportunity stage values, which we configure in the Twenty workspace before migration. If WayMore Deals reference a Company, we link the Opportunity to the corresponding Twenty Company via the workspaceId reference.

WayMore custom properties on Contact and Company records map to Twenty custom fields on People and Company objects. We create the custom fields in Twenty's Data Model before importing records. Type preservation (text, number, date, single-select, multi-select) requires field-by-field review because WayMore CSV exports do not carry field type metadata. We flag any fields where type cannot be determined from the source data and recommend a default mapping during scoping.

WayMore email campaign records (subject, content, send history) do not have a direct functional equivalent in Twenty CRM, which does not include native email campaign management. We export campaign metadata and content as structured documentation and attach it as a Note on the associated Twenty People records, or deliver it as a supplementary CSV so that the customer's admin can reference the content when rebuilding campaigns in an email platform of their choice.

WayMore SMS campaign records and message templates export via CSV. Twenty CRM does not have native SMS campaign management. We export SMS template content and opt-out status as structured data attached to the associated Twenty People records, preserving opt-out compliance data. The customer uses the migrated opt-out status to configure their chosen SMS platform.

WayMore segments are defined by dynamic rules that update automatically based on contact behavior. These dynamic rules cannot be replicated in Twenty's data model, which does not include a native segmentation engine. We export the current membership list for each WayMore segment as a static CSV of contact identifiers and deliver it as a named static filter in Twenty, or as a tag applied to the relevant People records. The segment will not auto-update after migration without manual reconfiguration in Twenty.

WayMore tags applied to Contacts for labeling and filtering map directly to Twenty Tags on People records. We extract tag names from the CSV export and apply them to the corresponding Twenty People records during migration. Tags used for marketing categorization (e.g., campaign source, list membership) are preserved as tags in Twenty alongside any new tagging schema the customer defines.

WayMore automation workflows include triggers, conditions, delays, and actions governing customer journey behavior. These workflow definitions and execution state cannot migrate to Twenty because Twenty does not include a native workflow automation engine in its CRM core. We export workflow structure as structured JSON documentation covering trigger type, conditions, step sequence, and actions for each active workflow. We deliver this as a rebuild guide the customer's admin uses to implement equivalent automation using their chosen external tooling (e.g., n8n, Make, or custom scripts). Any pending execution state at cutover is lost.

WayMore chatbot AI flows use a visual builder with decision trees and conversation logic. We export the flow structure and decision tree as structured documentation. Active chatbot sessions and conversation history do not transfer to Twenty. The customer receives a chatbot flow inventory document they can use to rebuild flows in their chosen chatbot platform or conversational AI tooling.

WayMore lead capture forms collect contact data and trigger automations. Form definitions (field structure, submission logic) export as documentation. The form-to-automation connections require manual reconfiguration at the destination. We deliver a form inventory with field mappings the customer uses to recreate forms in their chosen form platform and reconnect them to any rebuilt automations.