Migrate from Datacor CRM to Salesforce Sales Cloud

Datacor CRM Contacts are the primary customer record and include chemical-industry-specific fields: regulatory compliance contacts, shipping addresses, and EDI readiness flags. We map these to Salesforce Contact with the standard fields (FirstName, LastName, Email, Phone) and create custom fields for compliance-related attributes. Address data from Datacor's shipping address structure maps to Salesforce MailingAddress and ShippingAddress fields. Regulatory compliance flags migrate to custom checkbox fields that the customer's admin pre-defines before migration.

Datacor CRM Accounts represent chemical distributors and manufacturers with fields for industry classification, regulatory certifications, and parent-subsidiary hierarchies. We map Account to Salesforce Account with the Name, Industry, Type, and Website fields preserved. Parent-subsidiary hierarchy migrates to Salesforce's Account Hierarchy via ParentId. Industry classification maps to a custom picklist if Datacor's taxonomy does not map cleanly to Salesforce's standard Industry picklist values. Regulatory certifications (ISO, REACH, TSCA compliance flags) migrate to custom fields on Account.

Datacor CRM Opportunities track chemical sales cycles that can be 30-180+ days with multi-stage approvals for hazardous material quotes. We map stage names and preserve close dates, probability percentages, and amounts. Stage names in Datacor are chemical-industry-specific (Hazardous Material Review, Regulatory Approval, SDS Distribution) and map to Salesforce Opportunity StageName values that we configure as a custom Sales Process before migration. Probability percentages round to Salesforce's allowed integer range. Amount maps to Amount; if the source uses a different currency, we apply the exchange rate valid on the migration date.

Datacor CRM Quotes are integrated with the ERP's pricing engine and reference product formulations, quantities, and regulatory specifications. We extract quote headers, line items, and totals. Quotes migrate to Salesforce Quote objects (available on Professional tier and above). Quote status maps to Salesforce QuoteStatus. The ERP pricing reference field does not have a Salesforce equivalent; we preserve it as a custom text field quote_erp_reference__c. Quote PDFs migrate as ContentDocument attached to the Quote record.

Datacor CRM Quote line items carry chemical attributes per line: CAS numbers, hazard classifications, quantity, unit of measure, and regulatory annotations. Many destination CRMs represent opportunity products as a simple quantity-times-price relationship. We flatten complex quote line items into Salesforce OpportunityLineItem (Quantity, UnitPrice, TotalPrice) and preserve per-line hazard and regulatory annotations in custom fields on OpportunityLineItem (hazard_class__c, cas_number__c, regulatory_note__c). The customer must pre-create these custom fields before migration scope is confirmed.

Datacor CRM Cases manage customer service requests and complaint tracking for chemical distribution: material quality complaints, SDS document requests, regulatory compliance inquiries. We preserve case status, assignment, description, and related contacts. Case-thread email history may export as plain text from Datacor's UI; we map this to Salesforce CaseComments and EmailMessages linked to the Case. Priority and origin map to Salesforce Case Priority and Origin picklists.

Datacor CRM Product records carry chemical-specific attributes: CAS Registry Numbers, GHS hazard classifications, SDS document links, formulation data, and lot tracking identifiers. These fields have no standard equivalent in Salesforce. We create custom fields on Product2 (cas_number__c, ghs_classification__c, sds_document_url__c, formulation_data__c, lot_tracking_id__c) before migration. The product name, product code (SKU), and standard price migrate to Product2 Name, ProductCode, and StandardPriceBook entries.

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. Call duration and disposition migrate to custom fields on Task (call_duration_seconds__c, call_disposition__c). Activity sequences or follow-up chains from Datacor's task grouping do not map to Salesforce natively; we document the sequence as a chain of related Tasks linked by a custom parent_task__c lookup field.

Datacor CRM meeting records map to Salesforce Event. We preserve StartDateTime, EndDateTime, Location, and subject. Attendee information from Datacor's meeting records links to EventRelation records pointing at the resolved Contacts and Users. Meeting notes migrate to Event Description. If Datacor's meeting records include chemical-specific agenda items (regulatory review, SDS distribution), these migrate to a custom field meeting_agenda_note__c on Event.

Datacor CRM does not expose a documented bulk attachment export endpoint via its API layer. Attachments stored in the CRM are exported individually per record. We include attachment file names and URLs in the migration inventory, then upload files to Salesforce as ContentDocument records linked via ContentDocumentLink to the parent record (Contact, Account, Opportunity, Case, or Product). If Datacor's attachment URLs expire or are inaccessible post-migration, we flag them for manual re-upload. We do not guarantee attachment binary integrity for files exceeding 25 MB per Salesforce ContentDocument limits.

Datacor CRM owner records map to Salesforce User. We resolve owners by email match against the destination Salesforce org's User table. Any Datacor owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. If the customer uses inactive users in Datacor for historical records, we map those to Salesforce Users with IsActive=false and note that the records will appear under that inactive user until reassignment.

Datacor CRM is designed to share a data layer with Datacor ERP. Customer records, product records, and pricing may be co-stored in the ERP with the CRM surfacing views of that data. When migrating away, we must determine which records live in the CRM layer versus the ERP layer. Extracting from the wrong layer results in duplicate records or incomplete histories. We scope the migration by querying both layers and deduplicating on customer ID before writing to Salesforce. ERP-specific financial records (invoices, purchase orders, inventory quantities) are excluded from the CRM migration scope unless explicitly requested; they belong in the ERP, not in Salesforce.

If Datacor CRM holds custom objects beyond the standard Contact, Account, Opportunity, Quote, Case, and Product schema, we create equivalent custom objects in Salesforce with the __c suffix before migration. We pre-create all custom fields, lookup relationships to standard objects, and validation rules in a Sandbox org for testing before production deployment. Custom object migrations require a schema inventory from the customer before scoping begins.