Migrate from Daffodil CRM to Nutshell

Discovery and export method confirmation

We audit the customer's current Daffodil CRM instance by requesting a full field inventory (CSV headers, field types, sample records) and identifying the export path. If the customer has an active vendor relationship with Daffodil Software, we coordinate CSV export directly with their team. If not, we explore admin-panel export options or database-level access. We also confirm the target Nutshell account, the number of active Users to be provisioned, and the desired import order (Companies before People before Deals before Activities). The discovery output is a written migration scope with a confirmed export method and a custom field mapping matrix.

Export extraction and data quality assessment

We extract data from Daffodil CRM in dependency order: Companies first, then People (Contacts), then Deals, then Activities, then Tags. Each export is assessed for completeness, format consistency, and duplicate presence. We run a row-count reconciliation against the customer's estimate and flag any records with missing required fields (Contacts without email, Deals without amount, etc.) for the customer's review. Data quality issues are documented and either corrected by the customer or handled during the transform phase.

Transform and contact-company lookup resolution

We transform the Daffodil export CSVs into Nutshell's expected column headers. The critical transform step is resolving the Contact-to-Company relationship: we match Contact rows against the Company export using company name as the dedupe key, normalizing names to handle spacing and capitalization variations. We assign Nutshell-compatible external IDs to every record during transform so that Activity records can reference the correct Person and Deal IDs during the later import phase. Custom fields are type-checked and reformatted (date formats, picklist values) to match Nutshell's validation requirements.

Custom field provisioning in Nutshell

We create Nutshell custom fields matching the Daffodil custom field schema before any record import begins. This includes dropdown option values for picklist fields, number format settings for numeric fields, and date format configurations for date fields. Custom field provisioning happens in a staging or development Nutshell environment first to validate the schema before production migration. The customer reviews the custom field setup and approves before we proceed to record import.

Production import in dependency order

We import into Nutshell in record-dependency order: Companies first, then People (with company assignment resolved), then Deals (with owner assignment resolved), then Activities (with parent Person and Deal references resolved), then Tags. Each phase emits a row-count report. We run the import in batches of 2,000 records to stay within Nutshell's import limits and re-queue any failed rows with error codes for the customer to review. Duplicate records are flagged rather than re-imported to avoid inflating record counts.

Cutover, validation, and automation rebuild handoff

We freeze Daffodil CRM writes during cutover, run a final delta migration of any records created or modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of any Daffodil workflow configurations or automation logic that cannot be exported as structured data. This inventory lists each automation's trigger conditions and recommended Nutshell equivalent, but the rebuild itself is outside migration scope and is handled by the customer's admin team. We support a three-day post-cutover validation window where we resolve record count discrepancies and reconciliation issues.