Migrate your OneHash CRM data

Contacts in OneHash follow standard ERPNext DocType conventions with first_name, last_name, email, phone, and organization linkage. We migrate Contact records 1:1 with field-level mapping to the destination schema. Custom contact fields are preserved as custom properties in the target system.

Leads are managed as a distinct DocType before conversion to Contact or Opportunity. We preserve the full lead history including source, status, and conversion log. The lead-to-contact merge relationship is re-established in the destination by matching the converted contact reference.

Opportunities track deal stages within Pipelines. We migrate stage names, amounts, probability, and party information. Pipeline stage ordering is preserved via a separate stage-sequence map applied at import time.

Quotations carry line items linked to Items, with tax templates and terms. We map Quotation items to the destination's equivalent object and preserve the quotation-to-opportunity linkage as a custom reference field.

Sales Orders reference both Customers and Items and carry delivery and billing status flags. Order item rows must be mapped field-by-field because OneHash allows custom Item fields that may not exist in the destination. We flag any Item not found in the target catalog for manual review.

Customers are organization-level records linked to Contacts. We migrate the Customer record with its billing/shipping addresses and map the associated Contact relationship to the destination's account-contact model.

Items include product/service definitions with pricing, stock data, and custom attributes. Since OneHash Items can carry extensive custom fields specific to the business, we map standard fields (name, SKU, rate) and flag custom Item properties for manual schema alignment.

Employee records include designation, department, and salary structure. We preserve the org-chart relationships and effective-dated compensation records. HR-specific fields are mapped to the destination's Employee object where available.

Projects carry Tasks, assignees, and time tracking. We migrate project metadata and task hierarchy. Open vs. completed status is carried over; task-level comments are mapped as notes.

The Chart of Accounts defines the financial structure. We map account names, types, and parent-child hierarchy. Account numbers are preserved as-is where the destination supports them; otherwise they are stored as a custom property.

OneHash allows DocType-level custom fields via ERPNext's Customize Form tool. We extract all custom field definitions from the affected DocTypes and map them to the destination's custom property schema. Fields without a clear destination counterpart are flagged for manual review.

Documents attached to any DocType are migrated as binary blobs. We preserve the file name and linkage to the parent record. Large attachments may require chunked download and upload due to API payload limits.