Migrate from OneHash CRM to Twenty CRM

OneHash Contacts follow ERPNext DocType conventions with first_name, last_name, email, phone, and organization linkage. They map 1:1 to Twenty's Person object. The OneHash organization linkage (stored as customer_name reference) resolves to a Twenty Organization record that we create before Person import so the relationship is satisfied at insert time. Email deduplication applies if duplicate Person records share the same email address.

OneHash Leads are a distinct DocType before conversion to Contact or Opportunity. We preserve the full lead history including source, status, and conversion log. The lead_status property maps to Twenty's Lead status field. Conversion metadata (converted_to_contact, converted_to_opportunity timestamps) migrates as custom fields on the Lead record if the customer requires the audit trail.

OneHash Opportunities track deal stages within Pipelines. We migrate stage names, amounts, probability, and party information (contact and organization references). Pipeline stage ordering is preserved via a stage-sequence map applied at import. OneHash opportunity_amount, probability, and weighted_amount map to Twenty's amount, probabilityPercent, and a computed pipeline value respectively.

OneHash Quotations carry line items linked to Items, with tax templates and terms. We map quotation line items to Twenty custom fields or a custom Quote object that we create in the destination schema. The quotation-to-opportunity linkage is preserved as a custom relationship field on the Opportunity. PDF attachments on Quotations migrate as file blobs linked to the parent record.

OneHash Sales Orders reference both Customers and Items and carry delivery and billing status flags. Order item rows map field-by-field. Since OneHash allows custom Item fields that may not exist in Twenty's standard schema, we pre-create any required custom fields on the destination Order object before import. Delivery and billing status flags transfer as custom status fields.

OneHash Customers are organization-level records linked to Contacts. We migrate the Customer record with its billing and shipping addresses and map the associated Contact relationship to Twenty's Person-Organization linkage. Organization domain from the Customer record maps to Twenty's domain field for enrichment compatibility.

OneHash Items include product and 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, item_code, description, standard_rate) to a Twenty custom Product object and preserve custom attributes as additional custom fields on that object. Stock quantity fields are mapped where Twenty's schema supports them.

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 during export. Custom field definitions are recreated in Twenty's schema before data import.

Documents attached to any DocType migrate as binary blobs. We preserve the filename and linkage to the parent record. Large attachments may require chunked download and upload due to API payload limits. We verify attachment integrity via checksum before upload and flag any attachments exceeding Twenty's file size limits for manual handoff.

Employee records include designation, department, and salary structure. This is an ERP module object, not a CRM core object. We do not migrate Employees as part of standard scope. We deliver a written record of all Employee DocType fields and their definitions for the customer's admin to assess whether a separate HR migration or manual entry is appropriate in Twenty or a dedicated HR tool.