Migrate from MiniCRM to Twenty CRM

MiniCRM Cards are the primary record container and can hold contact details, company associations, deal associations, notes, tasks, and custom fields simultaneously. We analyze each Card's field composition during scoping to determine whether it is primarily a contact record (maps to Twenty People), a company record (maps to Twenty Company), or a hybrid that requires a Card-to-People plus Card-to-Company approach. We create both records and link them in Twenty. Polish-language card labels and custom field names are scoped with the customer's team before mapping.

MiniCRM Contact-level fields (name, email, phone, address) map directly to Twenty People. We preserve the full name split into firstName and lastName where available, or combine into the name field. Email maps to Twenty's email field; phone maps to phone. If MiniCRM stores multiple phone types (mobile, work, home), we map the primary to phone and secondary to a custom field.

MiniCRM Company records (Firmy) map to Twenty Company. The company name maps to Twenty's name field. Industry, address, and website fields map directly where present. Company records in MiniCRM may have fewer normalized fields than Twenty's Company schema; we map available fields and flag gaps during scoping. Custom company properties require field-level mapping to Twenty custom fields on the Company object.

MiniCRM Deals (Interesy) are associated with Cards and represent pipeline values. They map to Twenty Opportunity records. HubSpot-style dealstage and pipeline names from MiniCRM require mapping to Twenty's Opportunity stage values, which are configured in the destination workspace before import. Deal amount, close date, and probability map to Twenty's amount, closeDate, and probability fields.

MiniCRM Tasks are assignable to users and linked to Cards. Due date, status, assignee (via worker/Pracownik lookup), and description migrate to Twenty Task. Task recurrence patterns and reminder settings require explicit mapping since these may not have a direct Twenty equivalent; we document the original values and flag them for manual configuration in Twenty's task settings.

Free-text Notes attached to Cards migrate as long-text Note records in Twenty, linked via the parent record reference to the corresponding People, Company, or Opportunity record. We preserve the original timestamp and author where available. Polish-language note content migrates as-is without translation; the customer's team reviews during validation.

MiniCRM supports custom fields on Cards added via Settings. Field types include text, number, date, and choice. We detect and map each custom field to Twenty's custom field schema. Choice fields in MiniCRM require value mapping to match Twenty's select option values. Fields must exist in Twenty Settings → Data Model before import; we create the schema first and validate before data migration begins. Twenty's free self-hosted tier includes full custom field support without tier gating.

MiniCRM's trigger/action automation rules (e.g., 'when card enters status X, send email and assign task') do not export via any documented endpoint. We do not migrate automation rules. We document every active automation rule during discovery — capturing the trigger type, conditions, actions, and affected Card types — and deliver a written inventory with recommended Twenty Workflow equivalents. The customer's admin rebuilds these in Twenty's Workflow builder post-migration. This is explicitly a rebuild step, not a transfer.

MiniCRM User records include name, email, and role. We map these to Twenty Members in Settings → Members. Role distinctions in MiniCRM may not map directly to Twenty's permission model; we document the role mapping and flag any gaps. Members must be invited and active in Twenty before any OwnerId references can be resolved during record import. We coordinate user provisioning timing with the record migration sequence.

Calendar events and meeting records associated with Cards or Contacts migrate as Twenty Task records (with type meeting) or Event records depending on the customer's chosen configuration. We migrate event title, date, location, and linked Contact; full attendee lists require supplementary mapping and may need manual addition in Twenty if MiniCRM's attendee export is incomplete.

File attachments stored against Cards can migrate where MiniCRM exposes them via export. We flag any attachment size limits during scoping and map file references to Twenty's attachment handling. If MiniCRM's export does not include file binary content (only references), we document the attachment list for the customer to re-upload manually post-migration.

Tags applied to Cards for segmentation migrate as Twenty Tags. We deduplicate tags during import to avoid recreating a messy taxonomy in the new system. The customer chooses between a flat tag structure and a hierarchical label approach during scoping based on how they currently use tags in MiniCRM.