Migrate from OneHash CRM to Nutshell

OneHash Leads map directly to Nutshell People records with status set to lead. We preserve lead source, lead status, and conversion timestamp. If the Lead was converted to a Contact in OneHash, we migrate the Contact instead and drop the original Lead record to avoid duplication. The lead_score custom property (if present) migrates to a Nutshell custom numeric field on People.

OneHash Contacts map to Nutshell People with full name, email, phone, and address fields preserved. The organization linkage (Contact's link to Customer DocType) resolves to the Nutshell Company lookup after the Company import phase. Nutshell People do not have a separate Contact object, so the distinction between primary and secondary contacts within OneHash is preserved via a custom role field.

OneHash Customer records (organization-level accounts) map to Nutshell Company. We preserve customer name, website, billing address, and shipping address. The customer territory and industry custom fields (if present in the DocType) migrate to Nutshell custom fields on Company. Company is imported before People so that the Company lookup on People is satisfied at insert time.

OneHash Opportunities map to Nutshell Deals. The opportunity amount in INR is normalized to USD using the customer's specified exchange rate and stored as USD in Nutshell. Pipeline stage names from OneHash map to Nutshell Deal stage values via a stage-mapping table defined during scoping. Probability and expected close date migrate directly.

OneHash Quotations carry line items linked to Items DocType. We migrate quotation header fields (quotation number, date, party, currency, terms) and create a Nutshell Quote record. Quotation line items map to Quote line items with product name, quantity, rate, and amount. Tax templates from OneHash are noted as a text field because Nutshell Quotes do not have a native tax template engine.

OneHash Sales Orders reference both Customer and Items and carry delivery and billing status. We treat closed-won Sales Orders as Won Deals in Nutshell, preserving the order number and amount. The line item rows map to the Deal as a note attachment listing products and quantities, because Nutshell Deals do not support line-item structures. Open Sales Orders are migrated as active Deals with the order number stored in a custom field.

OneHash Items (product and service definitions) map to Nutshell Products. We migrate item name, item code, description, standard rate, and unit of measure. OneHash allows custom fields per Item DocType; we pre-discover these during schema discovery and create matching custom fields on Nutshell Product. Item stock data (if present) is noted but does not migrate because Nutshell does not have native inventory management.

OneHash Employee records (designation, department, email) map to Nutshell User provisioning. We extract the employee email and map designation to Nutshell role (Admin or Standard). Salary structure and compensation fields do not migrate because Nutshell is a sales CRM, not an HR system. The customer's admin provisions the actual Nutshell users after we deliver the employee-to-user mapping list.

OneHash Projects with task hierarchies migrate to Nutshell as a grouped task structure. The project name becomes a Nutshell Activity or a custom field grouping. Individual project tasks migrate as Nutshell Tasks with assignees, due dates, and status preserved. Time tracking entries from OneHash are migrated as task notes with duration. Open vs. completed status carries over directly.

OneHash allows unlimited custom fields per DocType via ERPNext's Customize Form tool. We run a pre-migration discovery pass that introspects each active DocType's custom field definitions via the API before mapping. Custom fields that map to People, Companies, Deals, or Products in Nutshell are created as typed custom fields during the schema phase. Custom fields that reference unsupported ERPNext objects are flagged for the customer's admin to handle post-migration.