Migrate from noCRM.io to Twenty CRM

noCRM Leads split into Twenty People records (the individual contact) and, where company context exists, Twenty Company records. Each Lead's email domain drives the Company match or creation. The original noCRM Lead status (Won, Lost, Cancelled, To-Do, Standby) maps to Opportunity stage on the related Opportunity record, with Won and Lost becoming closed stages and To-Do/Standby mapped to the customer's chosen open stages. We preserve the original noCRM Lead ID as a custom field nocrm_lead_id__c on both People and Opportunity for audit.

noCRM Pipeline Steps map to Twenty Opportunity stages. Each Step becomes a Stage in Twenty's Opportunity pipeline, with the step order preserved. Transition timestamps from noCRM migrate as Opportunity stage-change history or as comments on the Opportunity record. Pipeline-level probabilities migrate to stage probability fields if configured in noCRM.

noCRM Pipelines (multiple on Expert/Dream, one on Starter) map to Twenty Opportunity Pipelines. We pre-create Pipelines in Twenty Settings before Opportunity import. Starter accounts with a single pipeline map directly; multi-pipeline accounts require pipeline selection during scoping if only one will be active post-migration.

noCRM Tags migrate to Twenty Topics with TopicAssignment records on People and Opportunities. If tags represent categorical data that should function as a filter field rather than a topic, we map them to a multi-select custom field on People or Opportunity instead. The customer chooses the tag strategy during scoping based on how they use tags in noCRM.

Prospecting Lists from noCRM represent groups of Leads for outbound campaigns and reporting. We export list membership as a lookup relationship and recreate it in Twenty as workspace filters on the People object, or as static Segments if the list is small enough to function as a static group. Dynamic segments require rebuild in Twenty using its filter builder.

noCRM Lead activity logs (comments, status changes, step transitions) migrate as Note records linked to the corresponding People and Opportunity in Twenty. Timestamps and author attribution are preserved. Status-change events (e.g., To-Do to Won) that are discrete log entries rather than comments map to Opportunity stage changes with the original timestamp recorded.

Files attached to noCRM Leads migrate as Twenty File records attached to the corresponding People or Opportunity. File names and original upload dates are preserved. Large attachments may require chunked download from noCRM and re-upload to Twenty's file storage during migration.

noCRM Predefined Fields (custom lead fields configured in Admin > Sales process > Predefined Fields) vary per account. We extract the field definitions, create equivalent custom fields in Twenty Settings → Data Model before import, and map values during the People and Opportunity load. Field types map: text to TEXT, number to NUMBER, date to DATE, select to SINGLE_SELECT, multi-select to MULTI_SELECT.

noCRM Users assigned to Leads migrate as Twenty workspace Members. We resolve by email match. The customer's admin provisions Twenty Members before migration begins per Twenty's documentation requirement that users exist before owner references can map. Role and permission structures do not transfer and must be reconfigured in Twenty Settings → Workspace Members.

noCRM Custom Actions (account-specific menu items on lead cards that trigger workflows) do not have a standard schema and cannot be migrated as code. We document every Custom Action by name, trigger condition, and action destination, and deliver the inventory to the customer's admin for rebuild as Twenty Workflows or custom code post-migration. This documentation is included in the migration scope.

noCRM Statistics exports (company performance, team activity, forecasts) contain aggregate data that does not map to transactional records in Twenty. We export these as a separate dataset for the customer's reference and advise rebuilding reporting dashboards in Twenty's analytics module from migrated Opportunity and Activity data.