Migrate from Launchpad CRM to Nutshell

Export path confirmation and scoping

We audit Launchpad CRM's available export methods during the first call. We assess CSV export capability, direct database access permissions, and screen-scraping feasibility under explicit customer authorization. We also audit record counts (Clients, Cases, Programs, Services, Employers, custom fields), identify the deduplication candidates from redundant entry patterns, and confirm the target Nutshell tier based on the customer's team size and feature requirements. Scoping produces a written migration scope document, a preliminary mapping table, and a confirmed export method. This step typically takes one to two weeks depending on how quickly the customer provides export access.

Schema design and custom object configuration

We design the destination schema in Nutshell. This includes creating the Case__c custom object (or configuring Case notes strategy), defining custom fields on Person (eligibility flags, compliance codes), configuring pipeline stages to match program types, and creating Company records for Employers. Nutshell's custom field creation supports text, number, date, picklist, and multi-select types, which cover most Launchpad CRM custom property types. We validate the schema design in a Nutshell trial account or sandbox before production migration begins.

Data extraction and deduplication

We extract data from Launchpad CRM using the confirmed export path. We run a deduplication transform on Client records using the most recently updated field value as the canonical version, and flag records where the Case record contains newer data than the Client record. We validate record counts against the customer's system before transformation begins. This step produces a cleaned, transformed CSV or JSON file ready for Nutshell import.

Test migration and reconciliation

We run a test migration into the customer's Nutshell account using a subset of records (typically 100-500) representative of the full dataset. We validate that Person records are created correctly, Company links are resolved, Case__c records are associated to the correct Person, and custom fields are populated. The customer spot-checks 25-50 records against the Launchpad CRM source and signs off the mapping before production migration begins. Any corrections happen in the test phase, not in production.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated against Launchpad CRM Users by email), Companies (from Launchpad CRM Employers), People (from Launchpad CRM Clients with deduplication applied), Case__c records (with Person lookup resolved), Services (as Activity records linked to Person or Case__c), and Documents (as Note attachments). Each phase emits a row-count reconciliation report before the next phase begins. Owner assignments migrate by email resolution.

Cutover, delta migration, and rebuild handoff

We freeze the Launchpad CRM source during cutover, run a final delta migration of any records created or modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of HUD/RSA reporting linkages, automations, and scheduled exports requiring rebuild in Nutshell's report builder or a separate federal reporting tool. We do not rebuild automations or scheduled exports inside the migration scope. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team.