Migrate from CRUMP CRM to Twenty CRM

CRUMP CRM Contacts correspond directly to Twenty People. We export from the Dynamics 365 Contact entity, map standard fields (full name, email, phone, address) to Twenty's People object fields, and resolve the Owner lookup to a pre-invited Twenty Member by email match. Custom properties on Dynamics 365 Contacts require enumeration during audit and pre-creation in Twenty Settings before import.

CRUMP CRM Accounts map 1:1 to Twenty Companies. The account name becomes the Company name, and domain information maps to the website field. Parent-child account hierarchies in Dynamics 365 are preserved as Company relations in Twenty. We create the Company before any People import so that the relationship lookup is satisfied at insert time.

CRUMP CRM Deals correspond to Opportunities in Twenty. Deal value, close date, pipeline stage, and owner migrate directly. Stage names from Dynamics 365 are mapped to Twenty Opportunity stage values; if the destination pipeline does not yet exist we create it in Settings before migration. Closed-Won and Closed-Lost reasons migrate as custom Opportunity fields.

CRUMP CRM's Project Management module stores Projects as a distinct Dynamics 365 entity. We export Project records (name, status, start/end dates, assigned team members) and create a matching Custom Object in Twenty called Project. Task-level detail from the project module may be partial depending on Dynamics 365 licence tier; we document any truncated fields in the migration inventory.

Helpdesk tickets in CRUMP CRM are Cases in Dynamics 365 terminology. We export ticket status, priority, description, and linked contact. If the destination team uses Twenty's task model for support tracking we map to Tasks with a custom Ticket label field; otherwise we create a Ticket custom object and link it to the originating People record.

CRUMP CRM's bundled invoicing module stores Invoice records with line items, totals, and payment status. We export invoice data and create a matching Invoice custom object in Twenty. The relationship to the originating Deal or Project must be reconstructed from the export since Dynamics 365 may store these links in separate tables. We document the reconstructed relationship in the migration inventory.

Tasks exist across multiple CRUMP CRM modules (CRM tasks, project tasks, helpdesk tasks). We deduplicate and label each task by its origin module using a custom source_module field. Task status, priority, due date, and assignee migrate directly. HubSpot-style engagement notes are mapped to Twenty Notes linked to the parent record.

CRUMP CRM user accounts and role assignments require explicit mapping to Twenty Members. We resolve by email match. Inactive users in CRUMP CRM are archived rather than imported to avoid ghost records. The customer's admin must invite all active users to Twenty before the migration begins, per Twenty's documentation requirement that referenced users exist before Owner lookups can resolve.

Any custom entities created on top of Dynamics 365 are enumerated during the audit phase. Each custom entity and its fields are documented and mapped individually. We pre-create the matching custom object in Twenty Settings before import, including all custom fields and relationship fields, because Twenty requires fields to exist before CSV import can create records.

CRUMP CRM notes migrate to Twenty Notes linked via the relation system to the parent People, Company, or Opportunity record. Note body preserves rich text where supported. If the note has attachments these are flagged as a separate file-level pass since binary blob migration through the API layer requires additional handling.