Migrate from Resulticks to Twenty CRM

Resulticks Contacts map directly to Twenty People records via CSV import. We map standard fields (name, email, phone, address) and apply type-compatible transformations for phone number formats, date fields, and multi-select values. Resulticks custom Contact properties (legacy field types, computed fields, or multi-select attributes) require pre-creation in Twenty's Settings → Data Model before import. We inspect the Resulticks field schema during discovery, generate the equivalent Twenty field definitions, and validate that all custom fields exist in Twenty before the People import phase begins.

Resulticks Companies map to Twenty Company records 1:1. The Resulticks company domain becomes the Website field and serves as the dedupe key during import. Company must be imported before People so that the People-to-Company relationship (a many-to-one relation in Twenty) is satisfied at insert time. Twenty's standard Company object has minimal default fields; any industry classification, employee count, or annual revenue data from Resulticks requires pre-created custom fields.

Resulticks audience definitions (filter conditions on Contact attributes and behavioral events) do not export as portable logic. We preserve audience intent by exporting segment membership as a tag on each Contact record, then reconstructing equivalent filtered views in Twenty as custom filter views or tag-based groupings. The customer reviews the resulting segmentation map during sandbox validation and may choose to build permanent filter views in Twenty for recurring segment use cases.

Resulticks Contact-level Tags migrate as native Tags on Twenty People records. Tag counts and distribution are preserved at the Contact record level. Tags with high cardinality (more than 500 distinct values) are reviewed with the customer during scoping; we may consolidate low-frequency tags or flag them for the customer to selectively migrate.

Resulticks Campaigns represent the top-level execution unit for marketing sends and cannot map directly to a single Twenty object. We treat Campaign metadata (name, status, channel, schedule) as source context that may seed Opportunity records if the customer's sales process uses campaign-influenced opportunities. Campaign content assets and body templates require separate export and are documented as a manual content migration item for the customer's team.

Resulticks behavioral event history (page views, email opens, purchase events, custom track events) is migrated within a configurable event window agreed during scoping, typically the last 12-24 months. We normalize event types to a standardized schema and land them as Task records linked to the relevant People record, or as rows in a custom EventHistory object if the customer's data volume justifies a dedicated object. The configurable event window prevents unbounded import and controls migration cost.

Resulticks custom Contact properties vary by account configuration and may include legacy field types, multi-select values, or date-derived computed fields. We inspect the field schema during discovery, generate type-compatible Twenty field definitions (text, number, date, select, multi-select), create all fields in Twenty Settings → Data Model before import, and apply transformation logic for multi-select values and date formats during the People import phase.

Resulticks platform users map to Twenty Members by email lookup. The customer's admin must invite and provision all Members in Twenty before we run the People import so that owner assignment and record attribution are resolved correctly. We extract owner references from Contacts and Companies during discovery and reconcile against the provisioned Member list during scoping.

Resulticks Journey flows store branching logic, wait conditions, AI-driven Genie decision nodes, and multi-channel step sequences in a proprietary format with no export mechanism. We photograph and document the full Journey map during discovery and deliver this as a written reference architecture. The customer rebuilds flows in Twenty's workflow builder using the documented map as a guide. This item falls outside data migration scope; it is a separate configuration engagement.

If Resulticks stores product or service records (SKU, name, price, category), these migrate to a Twenty custom object pre-created during schema design. Product-to-Opportunity relationships are modeled as lookups or link fields. The specific data model depends on the customer's use case; we confirm during discovery whether products are used as standalone records or referenced within opportunity context.