Migrate from OneHash CRM to Salesforce Sales Cloud

OneHash Lead DocType maps directly to Salesforce Lead. The Lead's status, source, and conversion log migrate as Salesforce Lead Status and custom fields. We preserve the OneHash lead creation date in a custom field for audit. Since OneHash does not have a separate Contact object at the unqualified-prospect level, all unconverted Leads land directly in Salesforce Lead without a split rule, unlike HubSpot which requires Contact-to-Lead reconciliation.

OneHash Contact records map to Salesforce Contact with first_name, last_name, email, and phone preserved. The Contact's organization linkage (linked Customer DocType) maps to Salesforce AccountId via the Customer-to-Account lookup. We run Customer import before Contact import to satisfy the AccountId foreign key at Contact insert time.

OneHash Customer DocType (organization-level records) map to Salesforce Account. The Customer name becomes Account Name; billing and shipping addresses migrate to Account Address fields. Customer is created before Contact import so that AccountId is available at Contact insert. The Customer-territory or Customer-group field from OneHash maps to a custom Account field or Salesforce Territory if the customer uses territory management.

OneHash Opportunity DocType maps to Salesforce Opportunity. Stage names migrate to Salesforce StageName with probabilities mapped from OneHash stage_probability. The party linkage (Customer or Contact) resolves to AccountId and optionally ContactId. Pipeline stage ordering is preserved via a separate stage-sequence map applied at destination Salesforce configuration. If OneHash Opportunity tracks an amount in INR, we apply the customer's specified exchange rate at migration time.

OneHash Quotation DocType maps to Salesforce Quote, which is available from Salesforce Sales Cloud Professional tier. Quotation line items migrate as QuoteLineItems referencing Product2 and PricebookEntry. The quotation-to-opportunity linkage (one quotation per Opportunity in OneHash) maps to Salesforce Quote's OpportunityId lookup. Tax templates from OneHash become Salesforce Quote Tax fields or custom Quote Line Item tax fields.

OneHash Sales Order DocType maps to Salesforce Order, which requires the Salesforce Order Management add-on at additional cost. Line items migrate as OrderProducts referencing Product2. We flag this mapping during scoping because Salesforce Order is not included in all Sales Cloud editions. If the customer does not license Order Management, we map Sales Order fields to Opportunity custom fields and deliver a written note for the admin to evaluate the Order Management add-on.

OneHash Item DocType maps to Salesforce Product2. Item fields including item_name, item_code, description, and standard_rate map to Product2 Name, ProductCode, Description, and a custom standard_rate__c field respectively. We create Standard Pricebook entries during migration so that PricebookEntry records exist before any Opportunity or Quote line items reference them.

OneHash Employee DocType records migrate to Salesforce User. We resolve by matching the Employee's email address against the Salesforce User table. Any Employee without a matching User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Employee records carry designation, department, and compensation data that maps to Salesforce User fields and custom fields if the customer maintains org-chart information in Salesforce.

OneHash Project DocType maps to Salesforce Project only if the customer licenses Salesforce Shield (Field Audit Trail, Event Monitoring) or a Project Management Cloud add-on. Without one of these, we map Project to a custom Project__c object with Name, Status, StartDate, EndDate, and assigned team members as Contact lookups. The customer's admin decides during scoping which approach to take.

OneHash custom fields per DocType (added via ERPNext's Customize Form tool) are discovered via a pre-migration introspection pass that queries each DocType's field definitions via the OneHash API. We capture field name, field type, and options list, then map each to a Salesforce custom field of equivalent type (Text, Number, Date, Picklist, Checkbox). Custom fields are deployed to the destination Salesforce org's schema via Metadata API before any data import begins.

Documents attached to any OneHash DocType migrate as Salesforce Attachment records (for files under 25 MB) or ContentDocument records (for larger files via Salesforce Content). We preserve the file name, linkage to the parent record (by DocType-to-SObject mapping), and the original upload date as ActivityDate on the ContentVersion. Large attachments may require chunked download and re-upload due to API payload limits on both the source and destination.

OneHash Chart of Accounts defines the financial structure and is typically required only if the customer also migrates ERP data (beyond CRM) or plans to integrate with a Salesforce Financial Services Cloud add-on. We map account names, types, and parent-child hierarchy to a custom GL_Account__c object. Account numbers are preserved in a custom field. If the customer does not require GL data in Salesforce, we export the Chart of Accounts as a CSV inventory for the customer's finance team to import manually.