Migrate from MiniCRM to Nutshell

MiniCRM Cards are the primary record container and can hold contact details, deal information, custom fields, notes, and tasks simultaneously. We split each Card into a Nutshell Contact (for person/company identity) and, where deal values or pipeline stages exist, a related Nutshell Opportunity. The split logic is driven by whether the Card has an associated Interest (deal) record. We preserve Card-level custom field values by mapping them to Contact custom fields or Opportunity custom fields depending on which entity the field logically belongs to. Any Card without contact details becomes a Company-only record in Nutshell.

MiniCRM Contact fields (name, email, phone, address) map directly to Nutshell Contact fields. We use email as the deduplication key during import. If a Contact in MiniCRM is associated with a Company (Firma), we resolve the AccountId by matching the company name or domain. Nutshell's Contact object does not have a separate Lifecycle Stage property, so any stage or status value from MiniCRM maps to a custom Contact field for reporting purposes.

MiniCRM Company records map to Nutshell Account. Company name becomes the Account name; available address and domain fields map to Account address fields. MiniCRM Company records may have fewer normalized fields than typical CRM Accounts, so we flag any empty fields during scoping and confirm with the customer's team whether those fields were intentionally left blank or reflect incomplete data. We create Accounts before Contact import so that the Account relationship is satisfied at the moment of Contact insert.

MiniCRM Interests (Interesy) map to Nutshell Opportunities. The Interest name becomes the Opportunity name; deal value maps to Opportunity amount; pipeline stage maps to Opportunity stage. We document each MiniCRM pipeline stage name during discovery and map it to the nearest Nutshell stage value (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost). If MiniCRM pipeline stages do not map cleanly, we configure custom stage values in Nutshell before migration. Closed dates from Interests migrate to Nutshell's close date field.

MiniCRM Tasks linked to Cards migrate to Nutshell Tasks linked to the equivalent Contact or Opportunity. We preserve due date, status, assignee (mapped via email to Nutshell User), and description. Task recurrence patterns from MiniCRM are not preserved; we document any recurring task rules as a separate section in the handoff inventory. Reminder settings in MiniCRM do not transfer and should be rebuilt as Nutshell Tasks with reminder flags.

Free-text notes attached to MiniCRM Cards migrate to Nutshell Notes linked to the equivalent Contact, Account, or Opportunity. Note body transfers as plain text. Notes with Polish-language content retain the original text; we do not translate content. The association to the parent Card record is preserved by linking the Note to the corresponding Nutshell record during import.

MiniCRM custom fields on Cards (text, number, date, choice types) are detected during scoping and mapped to Nutshell Contact custom fields or Opportunity custom fields based on whether the custom field applies to person/company identity or deal tracking. Choice fields require explicit value mapping — we document each MiniCRM picklist value and its Nutshell equivalent during scoping. Choice fields that cannot map cleanly to Nutshell's supported custom field types (text, number, date, checkbox, dropdown) are flagged as a configuration risk item.

MiniCRM Users (Pracownicy) map to Nutshell Users by email match. Name and role from MiniCRM transfer to Nutshell User fields. Role distinctions in MiniCRM may not map directly to Nutshell's permission model; we document the role mapping during scoping and flag any role that has no direct Nutshell equivalent. Users without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Tags applied to MiniCRM Cards for segmentation migrate to Nutshell Tags on the equivalent Contact, Account, or Opportunity. We deduplicate tags during import to avoid recreating a messy taxonomy in Nutshell. If the customer has a large tag volume (over 500 distinct tags), we recommend a tag consolidation step during scoping to reduce noise in the destination.

File attachments stored against MiniCRM Cards can migrate where the platform exposes them via the integration endpoint or CSV export. We flag any attachment size limits during scoping. We map file references to Nutshell Attachments on the equivalent Contact, Account, or Opportunity record. If MiniCRM exposes attachment URLs rather than file content, we migrate the URL reference as a Note with a hyperlink rather than as a native Nutshell Attachment. Attachment metadata (filename, upload date, file size) is preserved where available.

MiniCRM automation rules (trigger/action workflows tied to card status changes, field fills, and deadlines) do not export via the documented API or integration endpoints. We document every active automation rule during discovery — including trigger, conditions, actions, and any delay or follow-up steps — and deliver a written inventory with recommended Nutshell equivalents (PowerDialer sequences, Task rules, or manual workflow notes). This is a rebuild scope, not a transfer. We prioritize documenting revenue-impacting sequences (deal stage triggers, follow-up reminders) first.