Migrate from Centrium CRM to Nutshell

Standard Centrium contact records (those without the organization flag) migrate directly to Nutshell Person records. All standard fields — name, email, phone, address, custom fields — transfer as text or typed fields where Nutshell's schema supports the type. We use email as the dedupe key during import. Contact-to-project and contact-to-deal associations preserve as Person links in Nutshell.

Centrium records flagged as organizations have no distinct object — they are contacts with an organization flag. We identify these records during preprocessing, create corresponding Company records in Nutshell, then re-link individual Contact records (those sharing the same organization flag) to the new Company via the Person-Company relationship. This preprocessing step extends the migration timeline for accounts with large organization lists. The organization's contact name typically becomes the Company name; the primary contact email becomes the Company email.

Centrium Deals map to Nutshell Leads or Opportunities depending on deal status and the customer's pipeline design. Open deals from Centrium map to Nutshell Leads or Pipeline (open) records; won deals map to Nutshell Won Opportunities; lost deals map to Nutshell Lost Opportunities. Centrium's flat status (won/open/lost) maps to the nearest equivalent Nutshell status. The deal name, value, associated contacts, and associated organizations transfer. Historical stage progression is not available because Centrium stores only a flat status without intermediate milestone timestamps.

Open and completed Centrium Tasks migrate to Nutshell Tasks with assignment, due date, completion status, and description preserved. Assignee resolution uses email matching against Nutshell User records provisioned before migration. Tasks without a matching assignee are assigned to the importing admin and flagged for manual reassignment. Completed tasks transfer with their completion date preserved.

Centrium Projects are lightweight containers linking tasks and contacts. Nutshell has no native Project object, so we map project membership to a Nutshell Company (if the project represents an organization relationship) or to a custom tagging strategy the customer selects during scoping. Project name and linked tasks/contacts transfer as a tag-based grouping or as notes on the linked records. Any project metadata beyond name and membership requires a custom field or note-based workaround.

Centrium Notes attached to contacts, deals, or projects migrate to Nutshell Notes linked to the corresponding Person, Lead, Opportunity, or Company record. Note body transfers as plain text. Notes are not threaded in Centrium, so multi-message conversations map as separate flat notes without conversational context preserved. Attachments within notes migrate as Nutshell attachment records linked to the same parent object.

Centrium custom fields are stored in a simplified schema with name-value pairs per record. We extract the field definition and values during the extract phase and apply a field-level map at import time, creating matching custom fields in Nutshell before data loads. Text, number, date, and checkbox field types map directly; multi-select or complex types map to text fields with a note in the validation report.

Files attached to contacts, deals, and projects in Centrium transfer to Nutshell Attachments linked to the corresponding record. We verify total attachment volume against the destination Nutshell plan's storage allocation before migration. If the customer's attachment library exceeds Nutshell's plan storage, we flag the gap and recommend either a plan upgrade or external archival of low-priority files before cutover. Attachments retrieved through the Centrium UI export are subject to the same manual download constraints as the record export.