Migrate from DinamikCRM to Twenty CRM

DinamikCRM Contact records map directly to Twenty Person. Standard fields (name, email, phone, address) map to their Twenty equivalents. We extract any custom fields attached to the Contact module during schema discovery and create matching custom fields in Twenty via the /metadata API before import. Contact ownership resolves by email match to a Twenty User record. The migration flags any DinamikCRM contact without an email address as requiring manual review in Twenty.

DinamikCRM Company records map to Twenty Company. The Company record is created before any Person import so that the Person's company link (company_id) is satisfied at insert time. We preserve any custom fields discovered on the Company module and map them to Twenty custom fields on the Company object.

DinamikCRM Lead records map to Twenty Person. Unlike Salesforce's Lead-Contact split, Twenty uses a single Person object for both prospects and customers. We map DinamikCRM lead status, source, and score fields to custom fields on the Person record so that the customer can segment prospects without a separate data model. The migration does not create a separate Lead object because Twenty does not include one as a standard entity.

DinamikCRM Deal records map to Twenty Opportunity. Deal value maps to opportunityAmount, deal stage maps to a Twenty pipeline stage, and owner maps via email resolution to the Twenty User. We discover the pipeline stage names and order from DinamikCRM's active pipeline configuration during schema discovery and create matching stage values in Twenty before import.

Each DinamikCRM pipeline becomes a Twenty Opportunity pipeline with its stage values. We extract the stage order and probability percentages from DinamikCRM's pipeline configuration and create matching stages in Twenty via the Settings → Data Model panel. Stage probabilities are rounded to integer values that Twenty accepts.

DinamikCRM Activity records (calls, emails, meetings, tasks, notes) map to Twenty Task and Note records. Activity type determines the mapping: DinamikCRM task-type activities become Twenty Task; DinamikCRM note-type activities become Twenty Note. We preserve the original activity timestamp as the Task or Note creation date, and associate each record to the correct Person or Company via lookup resolution. Activity owner maps via email to the Twenty User.

DinamikCRM Appointment records include date, time, attendee, and status fields. We map appointments to Twenty Task records and add custom fields for appointment-specific properties (attendees, location, status) that we create in Twenty before migration. Scheduling-specific fields that have no direct Twenty equivalent are flagged as requiring manual review in the destination.

DinamikCRM Invoice records with line items, totals, and status map to Twenty Opportunity with custom fields for invoice number, line item data, and total amount. We extract the financial data during export and create corresponding custom fields in Twenty. Financial fields are flagged for validation after import because totals and tax calculations may require rounding adjustments.

Support tickets from DinamikCRM's DESK module include status, priority, assignee, and conversation threads. We map ticket status and priority to custom fields on a Twenty Task record, and conversation threads migrate as Note records attached to the Task. Assignee maps via email resolution to a Twenty User. If the customer needs a dedicated support object, we create a Twenty Custom Object during schema setup.

DinamikCRM's extensible module system means every account may have custom modules not present in any other account. During schema discovery we enumerate all active custom modules, extract their field definitions and types, and map each to a Twenty Custom Object via the /metadata API. Custom field types are mapped to their Twenty equivalents (text, number, date, select, multi-select, email, phone, URL). Module-to-module relationships map to Twenty Custom Object lookups where applicable.

DinamikCRM Feedback entries (customer feedback text and metadata) migrate as Twenty Note records attached to the related Person or Company. We preserve the feedback creation timestamp and any rating or category fields as custom fields on the Note.

DinamikCRM User records and owner assignments on Contacts, Companies, Deals, and Activities map to Twenty User records. We resolve owners by email match. Any DinamikCRM owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Twenty requires users to exist before owner lookups can be satisfied, which is a prerequisite for the record import phases.