Migrate from RETAINUSER CRM to Twenty CRM

RETAINUSER Contacts map directly to Twenty People records. Standard fields (name, email, phone, address) migrate 1:1. The RETAINUSER contact record type is preserved as a tag or custom field on the Twenty People record so the customer can filter for previously qualified contacts. Custom properties on contacts require field-level mapping; we extract the full custom field schema including field type and picklist values during discovery.

RETAINUSER Leads (captured via Facebook Forms, WhatsApp, or manual entry) map to Twenty People with a source tag indicating original record type. The lead status and assignment owner migrate as custom fields rather than native properties, since Twenty does not have a separate Lead object. If the customer relies on a lead-to-contact lifecycle, they use the source tag to requalify and requalify People in Twenty after migration.

RETAINUSER Company records map to Twenty Company. The company-to-contact linkage is preserved by exporting the association table and reconstructing it using Twenty's companyId field on each People record during import. Company domain, industry, employee count, and address fields migrate directly; custom company properties follow the same field mapping process as contact custom fields.

RETAINUSER Deals map to Twenty Opportunities. Pipeline stage maps to a custom field or stage configuration in Twenty; the original pipeline name is preserved as metadata. Deal value, currency, expected close date, and owner migrate as standard Opportunity fields. Deals without a linked Company receive a placeholder company reference pending manual review.

RETAINUSER pipeline configuration (stage names, stage order, win/loss criteria) is extracted during discovery and mapped to Twenty Opportunity stage values. We create stage configuration records in Twenty matching the RETAINUSER pipeline structure. Probability percentages migrate as a custom probability field if the customer requires stage-level probability tracking beyond Twenty's default.

RETAINUSER Activities (calls, emails, meetings, tasks, notes) split into Twenty Tasks for action-oriented records and Twenty Notes for informational entries. Call duration and disposition migrate as custom fields on the Task record. Meeting records carry StartDateTime and Location from the RETAINUSER activity timestamp. Emails logged as activities migrate as Notes with the email body preserved and a label indicating original record type.

RETAINUSER custom objects migrate to Twenty custom objects with API names matched to the source object names. We pre-create the destination schema in Twenty's data model including all custom fields, field types, picklist values, and lookup relationships before any data import. Custom object records with lookup dependencies on People or Company are imported last in the sequence.

Custom fields on RETAINUSER People, Company, and Opportunity records require pre-creation in Twenty's Settings before any CSV import. We extract the full custom field schema during discovery: field type, picklist options, default values, and required status. Text fields map to Twenty text, numeric fields to number, date fields to date, and picklist fields to select or multi-select with options migrated. Field-level value mapping handles any format differences (phone number formatting, date formats).

RETAINUSER Users migrate to Twenty Members. We resolve each RETAINUSER Owner by email match against the Twenty Members list. Any RETAINUSER user without a matching Twenty Member is held in a reconciliation queue for the customer to provision before the migration continues, because OwnerId references are required on Opportunity and Task records. Inactive RETAINUSER users are migrated as inactive Members rather than active seats.

RETAINUSER workflow rules are not portable across platforms. We document each active workflow as a JSON artifact specifying the trigger event, condition branches, action sequences, and delay rules. This specification is delivered to the customer's admin team for rebuild in Twenty's workflow builder. The rebuild work is outside standard migration scope and should be planned as a separate implementation phase.