Migrate from Contlo to Twenty CRM

Contlo Contacts map directly to Twenty People. Standard properties (email, firstName, lastName, phone, address) map to Twenty Person fields by field name. Custom properties on Contlo Contacts migrate as key-value pairs stored in Twenty's custom fields or as a JSON blob in a notes field if no direct type match exists. Segment memberships are preserved as tag strings on the Person record.

Contlo Segments are behavioral groupings used to target automations. We preserve each Contact's segment membership as tag strings on the Twenty Person record. Segment rules (AND/OR filter logic, behavioral conditions) do not migrate as executable logic; we document the rule structure as a written handoff so the customer can rebuild segmentation in Twenty using its filter and tag-based grouping capabilities.

Contlo Company records map 1:1 to Twenty Companies. Domain name from Contlo becomes the Website field on the Twenty Company record and is used as a dedupe key during import. Companies are created before Person import so that the Person-Company link is satisfied at insert time.

Contlo Deals map to Twenty Opportunities. The deal stage name maps to a Twenty pipeline stage. Closed-won and closed-lost reason properties from Contlo custom fields migrate to Twenty Opportunity custom fields. Note that Twenty has no automated incremental numbering system for Opportunities as of current release — we assign sequential IDs from a migration-generated range and document the mapping for the customer's admin to reconcile against any naming conventions.

Contlo Automations are event-triggered, multi-step journey flows with conditional branching and time-delay actions. Twenty's workflow capabilities are in active development and do not currently replicate Contlo's automation graph structure. We extract the full automation graph as structured JSON data — trigger type, conditions, action steps, delay rules — and deliver it as a written rebuild guide. The customer's admin or a certified Twenty partner rebuilds each automation.

Contlo Campaign records contain message templates, scheduling metadata, and delivery history. Template content migrates as Note records linked to the associated Person or Opportunity. Delivery logs, open/click counts, and conversion metrics export as a time-series dataset and are delivered as a CSV alongside the Twenty import for the customer to reference in reporting. The campaign scheduling logic is not executable in Twenty and is documented for manual rebuild.

Contlo Voice Agent configurations, routing logic, and voice settings extract as structured data. The agent logic itself depends on Contlo's proprietary AI infrastructure and cannot be migrated. We deliver a written Voice Agent inventory with configuration details so the customer can evaluate Twenty-compatible voice integration options (e.g., external telephony providers) post-migration.

Event-level data (opens, clicks, conversions, engagement timestamps) exports from Contlo as CSV. We preserve this as a time-series dataset linked to Person IDs so the destination can display historical engagement context. The dataset does not become native Twenty records but is delivered alongside the migration for import into a reporting or BI tool.

Contlo custom fields on Contacts and Companies map to equivalent Twenty custom fields created during schema setup. We pre-create the destination custom fields with type-matched data types before any data import. Any Contlo custom property without a direct Twenty type equivalent is stored in a flexible text field with the original field name preserved as a label.

Contlo Owners map to Twenty User records by email match. Any Contlo Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Contlo's brand-owned generative AI Model is a proprietary platform artifact built from brand content and campaign training data. It lives in Contlo's infrastructure and cannot be exported as a portable artifact. We document this as a manual reconfiguration action item in the migration handoff. The customer must re-train or re-create an equivalent model in their chosen AI provider post-migration; Twenty CRM has no native generative AI layer.