Migrate from Cordis CRM to Nutshell

Cordis CRM Profiles map to Nutshell People (the Contact equivalent). Standard fields including name, email, phone, address, and any interaction history migrate directly. We flag any custom properties on Profiles during scoping and create equivalent custom fields in Nutshell before the data load. The dedupe key is email address, and Nutshell's duplicate detection handles matches based on email normalization.

Cordis CRM Companies map directly to Nutshell Organizations. The company name becomes the Organization name field. We preserve the relationship graph by exporting Company records first, then resolving the company reference on each Profile record during the load by matching on company name or a provided external ID. Any missing Organizations are created on the fly during the Profile import phase.

Cordis CRM Pipeline records with stages and statuses map to Nutshell Deals. The pipeline name becomes the Deal name or a custom field. Stage names from Cordis are mapped to Nutshell's default deal stages (New, Appointment Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost) or to custom stages if the customer has pre-configured them in Nutshell. We flag any stage count mismatch between Cordis and Nutshell during scoping.

Cordis CRM Tasks (both automated and manual) map to Nutshell Tasks. Task title, description, due date, status, and assignment migrate. Recurrence rules are not guaranteed to transfer because Cordis's recurrence model is not publicly documented; we migrate the next occurrence as a single task and flag the recurrence gap in the handoff document for the customer's admin to rebuild in Nutshell.

Cordis CRM documents attached to Profiles or Companies are exported as files and re-associated to the corresponding Nutshell Person or Organization record. We preserve the original filename and a link to the source record in a migration reference table. Document version history is not guaranteed to export cleanly from Cordis; we export the latest version and flag multi-version documents so the customer can decide whether to restore earlier versions manually. Version lineage is not preserved in the migration.

Cordis CRM Campaign records and membership data map to Nutshell Lists or Tags depending on how the customer intends to use the data post-migration. Campaign status and engagement dates migrate as metadata on the List or as Tag values. We survey the customer's campaign usage during scoping to determine whether Nutshell Lists or Tags is the appropriate target for their segmentation model.

Cordis CRM custom fields are not publicly documented in a schema reference, so we survey the customer's instance during scoping to identify all active custom fields, their data types, and their parent objects (Profile, Company, Pipeline, Task). We pre-create matching custom fields in Nutshell with equivalent data types before the main data load. Custom field limits vary by Nutshell plan; we flag any fields that may exceed the customer's plan limit and recommend a plan upgrade or field consolidation before migration.

File attachments linked to any Cordis CRM record (Profile, Company, Pipeline, Task) are exported individually and re-associated post-import using the record ID mapping table we build during extraction. We handle filename preservation and maintain a reference to the source Cordis record for audit. Attachments are loaded after all parent records are confirmed in Nutshell to avoid orphaned file references.