Migrate from OneHash CRM to Freshsales

OneHash Leads migrate directly to Freshsales Leads. The lead status, source, and conversion log transfer as custom fields if present. Freshsales enforces the Lead model: unqualified prospects live as Leads and convert to Contact, Account, and Deal via the built-in conversion action. We preserve the original OneHash lead creation date in a custom field on the Freshsales Lead for audit trail purposes.

OneHash Contacts follow ERPNext DocType conventions with first_name, last_name, email, phone, and organization linkage. We map these to Freshsales Contacts 1:1. If a OneHash Contact has an associated Customer (organization), we resolve that relationship during the Account migration pass and attach the Contact to the corresponding Freshsales Account by email domain matching.

OneHash Customer records map to Freshsales Accounts. The Customer record's billing and shipping addresses transfer to the Freshsales Account address fields. Freshsales supports multi-level account hierarchies (parent-child relationships) which OneHash does not natively expose; if the customer uses parent-company structures in OneHash via custom DocType links, we document them for manual hierarchy setup in Freshsales.

OneHash Opportunities track deal stages within Pipelines. We map Opportunity stage names to Freshsales Deal stages, amount fields to Amount, and party information to the linked Account or Contact. Pipeline stage ordering is preserved via a stage-sequence map applied at migration time. Closed-Lost and Closed-Won status from OneHash carry over to the equivalent Freshsales Deal status.

OneHash Quotations carry line items linked to Items, with tax templates and terms. Freshsales Deals can hold line items and notes but do not have a native quotation object. We migrate Quotation content as Deal notes and line items, preserving the quotation-to-opportunity linkage as a custom field linkage_map__c for reference. PDF attachments from quotations migrate as file attachments to the Deal.

OneHash Items include product and service definitions with pricing, stock data, and custom attributes. We map standard Item fields (name, item_code, description, standard_rate) to Freshsales Product records and create Standard Price Book entries for each item. OneHash custom Item fields require a pre-migration discovery pass to ensure the equivalent custom field exists in Freshsales before import.

OneHash Sales Orders reference Customers and Items and carry delivery and billing status flags. Freshsales does not have a native Sales Order object. We map Sales Order headers to Deals with the order number preserved in a custom field so_order__c, and line items attach to the Deal as Product entries. Order status flags migrate as Deal custom fields. This is a partial mapping; the customer admin may need to adjust Deal layouts for order-specific workflows.

OneHash allows unlimited custom fields per DocType via ERPNext's Customize Form tool. These fields do not appear in standard API responses unless explicitly requested. We run a pre-migration discovery pass that introspects each DocType's custom field definitions via the API before mapping, ensuring no custom property is dropped. We then pre-create matching custom fields in Freshsales with equivalent field types before the data import phase begins.