Migrate from OneHash CRM to HighLevel

OneHash Contacts follow ERPNext DocType conventions with first_name, last_name, email, phone, and organization linkage. We map these directly to GoHighLevel Contact fields and resolve the organization reference to a GoHighLevel Contact record if the business uses a flat contact model, or to a Company record if the destination is configured with account-contact linkage. Custom fields on the Contact DocType are discovered during the pre-migration schema pass and mapped to GoHighLevel custom fields on the Contact object.

OneHash Leads are a distinct DocType before conversion to Contact or Opportunity. We preserve the full lead history including source, status, and conversion log. Lead-to-contact merge relationships are preserved as GoHighLevel contact linkages where applicable. Any custom fields on the Lead DocType (discovered via ERPNext Customize Form introspection) migrate to GoHighLevel Lead custom fields.

OneHash Opportunities track deal stages within Pipelines. We migrate stage names, amounts, probability, and party information to GoHighLevel Opportunity records. Pipeline stage ordering is preserved via a stage-sequence map that we apply at import time. If GoHighLevel is configured with multiple pipelines, we map each OneHash pipeline to the corresponding GoHighLevel pipeline.

OneHash Quotations carry line items linked to Items, with tax templates and terms. We map quotation data to GoHighLevel Opportunity records where the destination uses a flat Opportunity model, or to a Custom Object where the customer requires line-item detail preserved separately. The quotation-to-opportunity linkage is preserved as a custom relationship field or note on the destination Opportunity.

OneHash Customers are organization-level records linked to Contacts. We map the Customer record to a GoHighLevel Company record with billing and shipping addresses. Associated Contact relationships map to GoHighLevel Contact records linked to the Company. If the GoHighLevel destination uses a flat contact model without accounts, we map Customer to Contact with organization details in custom fields.

OneHash Items include product and service definitions with pricing, stock data, and custom attributes. Standard fields (name, item_code, description, standard_rate) map to GoHighLevel Product records. Custom Item fields discovered during schema introspection map to GoHighLevel custom fields on Product or to a Custom Object if the business requires extended item attributes not supported by GoHighLevel's standard Product object.

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. All discovered custom fields are created in GoHighLevel's corresponding object before any data import, ensuring no custom property is dropped during export.

OneHash Projects carry Tasks, assignees, and time tracking. We migrate project metadata and task hierarchy to GoHighLevel Custom Objects if the destination org is configured for project management, or to Opportunity notes and tasks if the customer prefers to keep project context attached to the sales record. Open versus completed status is carried over; task-level comments are mapped as notes.