Migrate from NextCRM to Nutshell

NextCRM contact records map to Nutshell Person records. Standard fields including first name, last name, email address, phone number, and physical address transfer directly. We map NextCRM custom field values to their corresponding Nutshell custom fields on the Person object, creating the field definitions in Nutshell before import if they do not already exist. The Person's primary company assignment resolves through any linked Company record in NextCRM, creating or matching the corresponding Nutshell Company record first so the People-to-Company relationship is satisfied at insert time.

NextCRM Company records (open-source edition) map to Nutshell Company records. Company name, domain, industry, address, phone, and revenue fields transfer directly where the field names align. We use Company name as the dedupe key during import to prevent duplicate Company records from being created. Company records are inserted before any Person records to satisfy the People-to-Company lookup relationship.

NextCRM's multi-value tag system has no direct Nutshell equivalent. We resolve this in two ways during scoping: if the customer plans to use Nutshell Topics for taxonomy, we create TopicAssignment records during migration; if the customer prefers a flat text field, we migrate tags as a comma-separated string in a custom text field on the Person record. The choice depends on how the customer intends to filter and segment in Nutshell post-migration and is confirmed during discovery.

NextCRM list membership and Advanced Segmentation rules do not map 1:1 to Nutshell's native structure. Where a NextCRM list represents a static audience, we create a custom field on the Person record or a Nutshell List. Where segmentation rules are behavior-driven, we document the original logic during export and provide a written guide for recreating equivalent segments in Nutshell's filtering and reporting tools.

NextCRM custom field definitions and their values migrate alongside contact and company records. We map each NextCRM custom field type (text, number, date, checkbox, dropdown) to the closest Nutshell custom field type. Long-text values from NextCRM map to Nutshell's Long Text custom field type. Date fields preserve the original timestamp format during import. We create all custom field definitions in Nutshell before any data is inserted to prevent import failures from missing field definitions.

NextCRM campaign records transfer as Nutshell Campaign records, preserving campaign name, audience list, and campaign status. Active sends must be paused in NextCRM before cutover to prevent emails from routing to contacts that are mid-migration. We document the campaign structure and audience segment so the customer can recreate sends in Nutshell's email marketing tools. Campaign historical performance data (open rates, click rates) does not transfer as structured metrics and is noted in the campaign inventory document.

The NextCRM open-source edition's invoicing module (Invoice, Credit Note, Proforma, Receipt types) requires schema mapping to the destination. Nutshell does not include a native invoicing module, so invoice data transfers as a custom object or as document metadata attached to the relevant Company or Person record. Invoice line items and tax engine data are mapped field-by-field to the custom object schema. If the customer requires full invoicing capability post-migration, we recommend pairing Nutshell with a dedicated invoicing tool.

NextCRM project records, task assignments, and status fields migrate as Nutshell Tasks attached to the relevant Person or Company record, or as a custom Project object depending on the customer's Nutshell edition. We document project structure and task hierarchy during export so the relationship between records is preserved. Status transitions and assignment data transfer to the corresponding Nutshell task fields.

Document metadata and file references migrate to Nutshell as attachment records linked to the relevant Person or Company. Actual file storage depends on whether documents are hosted within NextCRM or linked externally. We migrate document filenames, descriptions, and linked record references; actual binary files are transferred through a file transfer mechanism agreed upon during scoping. Links to external hosted files are preserved as URL fields.