Migrate from DinamikCRM to Nutshell

DinamikCRM Contact records map to Nutshell Person. Standard fields (name, email, phone, address) map to Nutshell's name, email addresses, phone numbers, and postal addresses. Custom fields on DinamikCRM Contacts migrate to Nutshell custom fields on the Person object. We preserve the contact's original owner assignment via Nutshell's user lookup and flag any DinamikCRM contact ownership chains that require Nutshell user provisioning before import.

DinamikCRM Company records map to Nutshell Account. Company name, industry, website, and address fields migrate directly. DinamikCRM's company-contact relationship (linking a Contact to a Company) migrates as the Person-Account relationship in Nutshell. We resolve the Account lookup on each Person record at migration time using the company name as the dedupe key.

DinamikCRM Lead records map directly to Nutshell Lead. Lead status, source, and score fields migrate to Nutshell's standard Lead fields. Any DinamikCRM lead-specific custom fields migrate as custom fields on the Nutshell Lead object. Lead assignment to DinamikCRM owners maps via email resolution to Nutshell user records.

DinamikCRM Deal records map to Nutshell Deal. Deal name, value, stage, expected close date, and owner migrate directly. DinamikCRM's pipeline stage names map to Nutshell Deal status values. We configure Nutshell's pipeline stages to match DinamikCRM's stage names and probabilities before migration so deal history reflects the original pipeline structure. Deals are imported after their linked Person and Account records are in place.

DinamikCRM Activity log entries (call logs, email references, note entries) map to Nutshell Task records. Activity type, timestamp, description, and owner migrate as Task subject, due date, description, and assigned user. We preserve activity ordering by setting the Nutshell Task's completion date to the original DinamikCRM activity timestamp. Activity linking to the correct Person or Account uses Nutshell's built-in relation fields populated at migration time.

DinamikCRM Appointment records (date, time, attendee, status, location) map to Nutshell Event records where Nutshell Enterprise API is available. On lower Nutshell tiers without API access, appointments migrate as Tasks with the appointment flag set in a custom field and the original datetime preserved in description. Scheduling-specific fields like attendee type or recurrence rules that do not map directly to Nutshell Event are flagged for manual review during cutover.

DinamikCRM custom modules (customer-defined module structures unique to each account) require schema discovery before extraction. We enumerate all active custom module definitions, map each custom module to a standard Nutshell object augmented with custom fields, and flag any module-to-module relationships that cannot flatten into Nutshell's relational model. Many-to-many relationship modules migrate as tagged associations on the primary record using Nutshell's tagging system.

DinamikCRM pipeline configurations (stage names, stage order, stage probabilities) migrate to Nutshell Deal status values and pipeline layout. On Nutshell Foundation (one pipeline), all stages map into a single Nutshell pipeline. On Pro (five pipelines) and Enterprise (unlimited pipelines), we create separate Nutshell pipelines for each DinamikCRM pipeline if the account uses multiple sales pipelines. Stage probabilities migrate as deal-weight values in Nutshell's reporting setup.

DinamikCRM Invoice records with line items, totals, and status migrate to Nutshell Deal records using the deal value for the invoice total and custom fields for line item summaries. Financial fields requiring strict validation (tax amounts, payment status, invoice numbers) migrate as custom fields on the linked Deal, with a flag noting that financial record accuracy should be validated by the customer's finance team post-migration.

DinamikCRM user accounts and owner assignments map to Nutshell User records by email match. Any DinamikCRM owner referenced on a Contact, Company, Deal, or Activity record without a matching Nutshell User goes into a reconciliation queue for the customer to provision before migration resumes. We do not create Nutshell Users programmatically; the customer provisions them via the Nutshell admin panel.