Migrate from NextCRM to Twenty CRM

NextCRM Contact records map directly to Twenty People. Email address serves as the dedupe key during CSV import. All standard contact fields (name, phone, address) map to their Twenty People equivalents. Custom field values attached to Contact records migrate to corresponding custom fields on Twenty People, created in Settings before import. Note that Twenty requires custom fields to exist before CSV import; we create the full field schema in Settings as a pre-import step.

NextCRM Tag assignments on Contact records map to a multi-select custom field on Twenty People. We extract the full tag vocabulary from NextCRM, create a picklist or multi-select field in Twenty's Settings under People, then write each contact's tag list as a comma-separated or multi-select value during import. Where tags represent classification beyond what a multi-select field supports, we discuss Topics or a dedicated tag-based Custom Object with a lookup during scoping.

NextCRM List membership and Advanced Segmentation rules do not have a direct 1:1 equivalent in Twenty because Twenty's filtering operates on saved views rather than named segments with independent membership. We migrate list membership as a tag (see Tag mapping) so contacts retain their list affiliation. For Advanced Segmentation rules (behavior-driven segments that NextCRM evaluates dynamically), we document the rule logic in a written segment recreation guide for the customer's admin to implement as Twenty saved views.

NextCRM custom field definitions and values migrate to Twenty custom fields on the appropriate standard or custom object. We match field types: text to text, number to number, date to date, checkbox to boolean, dropdown to select. Multi-value custom fields map to Twenty's multi-select. The destination field must be created in Settings before import; we do this as a pre-import configuration step. Fields with no equivalent in Twenty are flagged for the customer to decide whether they belong on a Custom Object.

The NextCRM open-source nextcrm-app Invoice module (Invoice, Credit Note, Proforma, and Receipt types) has no direct Twenty standard object equivalent. We create a Custom Object named Invoice with fields for invoice number, series, line items, tax amounts, total, status, and the related Company lookup. Line items migrate as a related Custom Object or as a JSON-serialized field on the Invoice record depending on the customer's reporting needs. The Invoice series and tax engine data require field-level mapping during scoping.

NextCRM open-source Project records migrate to a Twenty Custom Object named Project. Task assignments and project status fields map to custom fields on the Project object with lookup relationships to People (for assignees) and Company (for the client). We preserve status labels, due dates, and priority flags from the source. If the customer uses a separate project management tool, we document the Project migration scope separately and recommend against duplicating project management in the CRM unless the use case specifically requires it.

NextCRM Document metadata and file references migrate to Twenty as file attachment fields or as external URL references stored on the related People, Company, or Custom Object record. We do not migrate actual binary file storage; we migrate the metadata and links. If documents are hosted within NextCRM, the customer must ensure the source files are preserved separately before decommissioning the old platform.

NextCRM Campaign records transfer as a Custom Object capturing campaign name, start date, audience, and status. Campaign audience membership migrates as tags on the related People records so the contact affiliation is preserved. Active sends must be paused before migration; we document the campaign structure and audience rules in a written recreation guide so campaigns can be re-created in Twenty's email integration or a connected marketing tool.

NextCRM Owner records map to Twenty User accounts. We resolve by email match. Any NextCRM Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Twenty requires that all referenced users exist before importing records that have an owner assignment.

NextCRM Visual Automation Builder workflows are platform-specific and cannot export. We document each workflow's trigger conditions, action steps, delay rules, and audience logic in a written recreation guide for the customer's admin to rebuild in Twenty's workflow builder. Active campaigns continue running during cutover, allowing a phased transition. The documentation includes recommended Twenty equivalents for each workflow action (create task, update field, send email, etc.). Email sequences are documented separately as a cadence rebuild guide.

NextCRM email sequences and follow-up automations are tied to the Visual Automation Builder and do not export. We extract the sequence logic, step order, step types (email, delay, task, condition), and timing rules and include them in the written sequence rebuild guide delivered with the migration package. Twenty's workflow builder and any connected email tool handle the rebuild; sequencing is a separate implementation scope.