Migrate from StrategicERP to Salesforce Sales Cloud

StrategicERP vendor and subcontractor records map 1:1 to Salesforce Accounts. Subcontractor specialty and trade category map to a custom pick-list field (Subcontractor_Trade__c). Primary contact from the ERP maps to the Account's primary Contact; additional contacts migrate as related Contact records.

StrategicERP vendor contact records map to Salesforce Contacts linked via AccountId lookup to the parent Account. Multiple contacts per vendor collapse to a single AccountId since Salesforce's Contact-Account model differs from ERP hierarchies. Email-match resolution assigns Contact owners to Salesforce users; unmatched contacts are flagged for team review before migration runs.

StrategicERP projects are the core entity with no direct Salesforce equivalent. If your team uses project records as a sales pipeline — tracking contract value, phase, and close date — they map to Salesforce Opportunities. If projects are operational records distinct from sales deals, a custom Project__c object with custom fields for phase, cost code, and budget is the correct target.

StrategicERP project phases (Pre-Construction, Design, Procurement, Construction, Closeout) map to Salesforce Opportunity Stage values via value-by-value mapping. Each stage probability and forecast category is re-applied from Salesforce's stage model to maintain forecast accuracy. Phase-entered timestamps preserve as a custom datetime field for historical continuity.

StrategicERP cost codes are construction accounting identifiers (e.g., 01-100 General Requirements, 03-200 Concrete) with no Salesforce CRM equivalent. If projects have line items tied to cost codes, they map to OpportunityLineItem (Product2 + Quantity + UnitPrice). Otherwise cost codes migrate as a custom text field (Cost_Code__c) on the Opportunity or Project__c object.

Purchase orders have no Salesforce standard object. They migrate as a custom Purchase_Order__c object with fields for PO number, vendor (AccountId), total amount, status, and issue date. A lookup to Opportunity or Project__c links the PO to the originating deal. Post-migration, Salesforce CPQ can replace the PO workflow for quote-to-cash processes.

Change orders — scope or budget changes on a project — have no Salesforce standard equivalent. They migrate as a Change_Order__c custom object with fields for description, approved amount, status, and a lookup to the parent Opportunity or Project__c. Original approval date and approver name are preserved as custom fields.

StrategicERP contract records (contract number, contract type, signed date, expiration) map to Salesforce Opportunity with additional custom fields: Contract_Type__c, Contract_Number__c, and Contract_Expiration__c. The ERP's contract document itself (PDF) is stored as a Salesforce File attached to the Opportunity. Additional metadata like contract value and renewal terms migrate as custom fields on the Opportunity.

StrategicERP equipment records map to Salesforce Asset objects. Equipment serial number maps to Asset.SerialNumber, category to Asset.Type, and status to Asset.Status. A lookup to Account ties equipment to the owning company. Note: Salesforce Asset is designed for customer-owned assets; map StrategicERP equipment as Asset only if it represents billable or trackable customer assets.

StrategicERP employee records (payroll, certifications, safety training) have no Salesforce standard equivalent. CRM-relevant employees (project managers, estimators) can be mapped to Salesforce Users by email match. Full HR data migrates as a custom Employee__c object or stays in StrategicERP and is accessed via integration.

StrategicERP file attachments (subcontractor certificates, POs, change orders, drawings) re-upload to Salesforce Files. File size limits apply — Salesforce default is 25MB per file. Inline images embedded in notes are extracted, downloaded, and rehosted to Salesforce's secure storage. Files exceeding the size limit may require compression or alternative storage solutions before upload.

StrategicERP work order or service records map to Salesforce Cases linked to the relevant Account or Opportunity via lookup relationships. Original work order number maps to Case.CaseNumber for traceability across systems. Status and priority map via value mapping to Salesforce Case Status and Priority pick-lists, ensuring consistency with existing case workflows and automation rules.