CRM migration
Field-level mapping, validation, and rollback between OneHash CRM and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
OneHash CRM
Source
monday CRM
Destination
Compatibility
6 of 11
objects map 1:1 between OneHash CRM and monday CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from OneHash CRM to Monday.com CRM is a migration from an ERPNext-forked data model to a board-based Work OS. OneHash organizes business data around DocTypes — Leads, Contacts, Opportunities, Quotations, Sales Orders, and Invoices — with a rigid inter-object relationship hierarchy inherited from ERPNext. Monday.com CRM uses boards, groups, and columns with item-level CRM cards that reference People (Contacts), Deals, and Activities. We resolve the schema translation during discovery: OneHash DocTypes become Monday.com boards, DocType fields become board columns, and custom fields are introspected via the ERPNext API before any column is created. Quotation-to-Sales Order chaining and ERPNext-style address linkages require custom board configurations in Monday.com. Workflows, automations, and HR/ERP modules (Employees, Chart of Accounts) do not migrate as code; we deliver a written board structure map and an automation rebuild guide for the customer's admin.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a OneHash CRM object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
OneHash CRM
Lead
monday CRM
Board (People CRM type)
1:1OneHash Leads map to Monday.com People records within a CRM board. The lead source, status, and conversion log fields migrate as custom columns on the board. Lead email, phone, and organization fields map to the Person column type. The lead-to-contact conversion relationship is represented by creating a linked Deal and associating it with the Person record; no automatic conversion trigger migrates because Monday.com does not have a Lead-to-Contact convert action.
OneHash CRM
Contact
monday CRM
People (CRM board)
1:1OneHash Contacts migrate as Monday.com People records. First name, last name, email, and phone map to the built-in Person column fields. Organization linkage (OneHash customer_name) becomes a linked person reference or is stored in a custom text column. Contact addresses from OneHash are stored as multi-line text columns in Monday.com because the platform does not have a structured address object.
OneHash CRM
Customer
monday CRM
Account or Organization (CRM board)
1:1OneHash Customers (organization-level records linked to Contacts) map to Monday.com as either Account-style text entries or as Organization column values on a Deals board. If the customer uses a separate Companies board, we create a Companies board and link People records to it. The decision is made during scoping based on the customer's CRM usage pattern.
OneHash CRM
Opportunity
monday CRM
Deal (CRM board)
1:1OneHash Opportunities migrate to Monday.com Deals. Deal stage maps to a Status column with stage values migrated from OneHash pipeline stages. Deal amount maps to a Number column; probability maps to a custom Number column or is omitted if the team does not use probability tracking. The Opportunity owner maps to an Assignee column by resolving the email match to a Monday.com workspace member.
OneHash CRM
Quotation
monday CRM
Board or custom structure
lossyOneHash Quotations carry line items linked to Items, tax templates, and terms. Monday.com does not have a native quotation object. We create a dedicated Quotations board with columns for client name (linked Person), quotation date, total amount, status, and line items stored as a sub-items group or as text summary. The customer decides during scoping whether quotation detail is captured at the board level or summarized.
OneHash CRM
Sales Order
monday CRM
Board or excluded
lossyOneHash Sales Orders reference Customers and Items with delivery and billing status flags. Monday.com has no native Sales Order object. We either create a Sales Orders board mirroring the Quotations board structure or exclude Sales Orders from migration scope if the customer confirms they do not track order fulfillment in OneHash. This decision is made during discovery.
OneHash CRM
Custom Fields (DocType-level)
monday CRM
Custom Columns
1:1OneHash custom fields per DocType are discovered via an API introspection pass before migration. Each custom field's ERPNext field type is mapped to the nearest Monday.com column type (text, number, date, person, link). Custom field values migrate as column values on the corresponding board. If a custom field references a linked DocType (e.g., a custom field on Contact linking to a Project), we map it as a text reference or create a linked board during schema design.
OneHash CRM
Item
monday CRM
Board or excluded
lossyOneHash Items include product/service definitions with pricing, stock data, and custom attributes. Monday.com does not have a native product catalog. Items are either excluded from migration scope or created as a read-only Items board if the customer needs to reference products on Deals or Quotations. The decision depends on whether the customer uses OneHash item pricing on Quotations.
OneHash CRM
Employee
monday CRM
Excluded or Board
lossyOneHash Employee records include designation, department, and salary structure. Monday.com has no HR module. Employee records are excluded from standard CRM migration scope unless the customer specifically requests an Employee directory board. If requested, we create a basic Employees board with name, designation, department, and email columns as text fields.
OneHash CRM
Project
monday CRM
Work Management Board
1:1OneHash Projects carry Tasks, assignees, and time tracking. Monday.com has strong work management capabilities. We migrate Project metadata and Task hierarchy as a Monday.com work management board. Open vs. completed status is preserved via a Status column. Task-level comments are stored as Updates on each item. Time tracking migrates as a Number column (hours) if the customer uses it.
OneHash CRM
Attachment
monday CRM
File column or excluded
lossyDocuments attached to OneHash DocTypes migrate as Monday.com file attachments via the file column type. Large attachments over Monday.com's file size limits (up to 250 MB per file on Pro plans) are flagged for the customer to host externally and link via URL column. We chunk large binary downloads from OneHash and re-upload via Monday.com's file API during migration.
| OneHash CRM | monday CRM | Compatibility | |
|---|---|---|---|
| Lead | Board (People CRM type)1:1 | Fully supported | |
| Contact | People (CRM board)1:1 | Fully supported | |
| Customer | Account or Organization (CRM board)1:1 | Fully supported | |
| Opportunity | Deal (CRM board)1:1 | Fully supported | |
| Quotation | Board or custom structurelossy | Fully supported | |
| Sales Order | Board or excludedlossy | Fully supported | |
| Custom Fields (DocType-level) | Custom Columns1:1 | Mapping required | |
| Item | Board or excludedlossy | Fully supported | |
| Employee | Excluded or Boardlossy | Fully supported | |
| Project | Work Management Board1:1 | Fully supported | |
| Attachment | File column or excludedlossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
OneHash CRM gotchas
OneHash is a fork of ERPNext with Indian-market pricing
Annual billing is mandatory for paid plans above the free tier
No publicly documented API rate limits or bulk export endpoints
Custom Fields are DocType-specific and require schema discovery
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and DocType introspection
We audit the OneHash account across DocTypes in use, custom field definitions per DocType (via ERPNext introspection endpoint), pipeline and stage configurations, and attachment volume. We pair this with a Monday.com workspace audit to identify existing boards and confirm CRM plan tier (Basic, Standard, or Pro). The discovery output is a written migration scope document listing every object to migrate, exclude, or configure, plus a preliminary board structure map for Monday.com.
Schema design and board structure mapping
We design the Monday.com board structure based on the discovery output. Each OneHash DocType becomes a Monday.com board. Standard fields map to built-in column types (person, number, date, status); custom fields map to custom columns with the nearest Monday.com type. We create placeholder boards for Quotations and Sales Orders (or exclude them based on the customer's scoping decision). Board sharing settings and team access are configured during this step.
API extraction with adaptive rate limiting
We extract data from OneHash using the ERPNext REST API. We begin with a schema discovery pass to enumerate all custom fields per DocType before extracting record data. We apply adaptive rate limiting: initial requests use a 500ms delay between calls, increasing to 2 seconds on any 429 response. Records are chunked into batches of 100 for extraction efficiency. Owner resolution by email is performed during extraction so that OwnerId references are ready for Monday.com import.
Sandbox migration and reconciliation
We run a full migration into a Monday.com test workspace using production-like data volume. The customer reconciles record counts, spot-checks 20-30 records against the OneHash source for field-level accuracy, and reviews board structure and column assignments. Any mapping corrections are made before production migration begins. This step validates that quotation boards and custom column types are correctly configured.
Production migration in board order
We run production migration in board dependency order: People (Contacts, Customers), Deals (Opportunities), custom boards (Quotations, Sales Orders, Projects), then attachments. Each board migration emits a row-count reconciliation report before the next board begins. Large attachments are chunked and uploaded via Monday.com's file API. Custom field data is imported after the standard fields to ensure the custom columns exist on the board at import time.
Cutover, validation, and automation rebuild handoff
We freeze OneHash writes during cutover, run a final delta migration of any records modified during the migration window, then enable Monday.com as the system of record. We deliver a written board structure document and an automation rebuild guide listing every OneHash workflow automation with its trigger, conditions, actions, and recommended Monday.com automation equivalent. We support a five-day hypercare window for reconciliation issues. Workflow rebuilds are handled by the customer's admin or a Monday.com partner; they are outside standard migration scope.
Platform deep dives
OneHash CRM
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across OneHash CRM and monday CRM.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
OneHash CRM: Not publicly documented — discovered dynamically during migration.
Data volume sensitivity
OneHash CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during OneHash CRM to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your OneHash CRM to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave OneHash CRM
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.