Migrate from Datacor CRM to Nutshell

Datacor CRM Accounts (representing chemical distributors and manufacturers) map to Nutshell Organizations. We extract Account records from the CRM data layer, not the ERP layer, to avoid co-mingled inventory or compliance records. The Account name, industry classification, regulatory certifications, parent-subsidiary hierarchy, and address fields map to Organization fields or pre-created custom fields. Parent-account references become Nutshell Organization links rather than a native subsidiary hierarchy, so the customer's admin notes the parent-child structure during scoping to maintain it manually or through a custom field.

Datacor CRM Contacts map to Nutshell People. Contact fields including regulatory compliance contacts, shipping addresses, EDI readiness flags, and the associated Account link map to Nutshell Person fields with Organization assignment resolved at migration time. We deduplicate contacts by email address before write and flag any contacts that appear in both the CRM and ERP layers for customer review.

Datacor CRM Opportunities (with chemical sales cycles of 30-180+ days and multi-stage approvals for hazardous material quotes) map to Nutshell Deals. Opportunity name, stage, close date, probability, amount, and owner migrate to corresponding Nutshell Deal fields. Stage names map through a configuration step where each Datacor stage value is assigned to a Nutshell stage in the destination pipeline. Probability percentages migrate as integer values.

Datacor CRM Quotes are tightly integrated with the ERP pricing engine and support multi-line specifications with chemical attributes per line. Nutshell does not have a native Quote object, so we flatten quote header and line item data into the Deal record. Multi-line chemical specifications with per-line hazard or regulatory annotations are simplified to quantity, unit price, and product reference; the original per-line annotation text is preserved in a custom Deal field for admin review. Quote PDFs are not imported via the standard path; we deliver a file manifest with URLs for manual upload to Nutshell Attachments.

Datacor CRM Products carry chemical-specific attributes: CAS Registry Numbers, GHS hazard classifications, SDS document references, and formulation data. These fields have no standard Nutshell equivalent. We pre-create custom fields on Nutshell Product records (cas_number__c, ghs_classification__c, sds_url__c) during schema setup before any data writes. Product name, SKU, and standard pricing migrate to Nutshell's native product fields. The customer should validate that the custom field types (text, URL, date) match the source data types during scoping.

Datacor CRM Cases (service tickets and complaint tracking) map to Nutshell Cases. Case status, assignment, description, related Contact or Account, and creation date migrate directly. Case-thread email history may export as plain text from Datacor's data layer; we import this as Case description appends or Notes linked to the Case rather than as threaded email records.

Datacor CRM call reports, logged activities, and task records export as date-stamped entries linked to Contacts or Accounts. We preserve activity type, date, owner, and description text. Activity sequences or multi-step engagement logs that Datacor tracks internally as process flows do not map to Nutshell's activity model and are delivered as a written inventory for the customer to rebuild manually in Nutshell.

Datacor CRM does not expose a documented bulk attachment export endpoint. We extract attachment file names and reference URLs from the CRM records and deliver a file manifest listing which Attachments exist, which record they belong to, and the recommended manual upload path in Nutshell. Customer-facing teams perform the manual upload step post-migration with guidance from our manifest.

CAS Registry Numbers, GHS hazard classifications, regulatory certification dates, EDI readiness flags, and SDS document links are chemical-industry-specific fields in Datacor CRM that have no Nutshell standard equivalents. We create custom fields on the appropriate Nutshell object (Person, Organization, Product) during the schema configuration step before any data import. Field types are mapped: text fields for CAS numbers and classification codes, URL fields for SDS document links, date fields for certification dates, and checkbox fields for EDI readiness flags. The customer validates field types against source data during scoping.