CRM migration
Field-level mapping, validation, and rollback between Close and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Close
Source
monday CRM
Destination
Compatibility
5 of 10
objects map 1:1 between Close and monday CRM.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Close to Monday.com CRM is a shift from a purpose-built sales communication tool to a flexible Work OS that offers CRM capabilities through board-and-column architecture. Close's unified inbox, built-in dialer stack, and lead-activity threading have no direct Monday equivalent, so we map call logs, SMS, and email history to activity items on the matching CRM board records. Close's Leads, Contacts, and Opportunities become People items and Deal items in Monday's CRM boards; pipeline stages become Status columns with probability values migrated as separate Number columns. Custom Activities and Custom Objects require pre-creation of their type definitions before data imports begin. We do not migrate Close Workflows or Sequences; we deliver a written inventory for the customer's admin to rebuild using Monday's Automation and Integrations layer.
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 Close 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.
Close
Lead
monday CRM
People item (CRM board)
1:1Close Leads map to People items in Monday's CRM board. We preserve the full lead record including name, email, phone, status label, and owner assignment as item columns. The lead status label is stored as a Status column value matching Close's status vocabulary. Owner assignment resolves by email against Monday workspace members.
Close
Contact
monday CRM
People item (CRM board)
1:1Close Contacts map to People items alongside Leads. Where the destination's CRM board supports separate People and Organization records, we model Contact as a Person item linked to the matched Organization item. Where Monday's native CRM People board is used, Contacts and Leads coexist with a Contact_Type column distinguishing them. Email, phone, organisation, and owner fields map to typed columns.
Close
Opportunity
monday CRM
Deal item (CRM board)
1:1Close Opportunities map to Deal items in Monday's CRM board. The opportunity value, expected close date, and owner assignment migrate to Deal item columns. The Close pipeline assignment determines which Monday CRM board receives the Deal item, and the Close stage name maps to a Status column value on the destination board.
Close
Pipeline
monday CRM
CRM board
1:1Each Close pipeline becomes a separate Monday CRM board. We create the board with a Name column matching the pipeline label and configure the Deal_Value, Expected_Close, and Owner columns that Monday CRM boards ship with by default. Any custom pipeline columns from Close are added as additional columns during board setup.
Close
Pipeline Stage
monday CRM
Status column value
lossyClose pipeline stages map to Status column values on the destination CRM board. Stage ordering is preserved by setting the Status column value sequence in Monday to match Close's stage display order. Stage probability weights migrate as a Number column (Stage_Probability) since Monday Status columns do not natively carry probability values.
Close
Activity (Call, Email, SMS, Task)
monday CRM
Activity sub-items or column updates
1:manyClose's activity history attached to Leads and Contacts is modelled as sub-items on the matching People item in Monday CRM, with the activity type stored as a Status or Label column and the timestamp, duration, and content preserved in text columns. Call recordings migrate as file attachments on the relevant activity sub-item. Note that Monday does not have a native unified inbox equivalent; activity sub-items provide a chronological list but not a threaded email-and-SMS view.
Close
Custom Field (Lead, Contact, Opportunity)
monday CRM
Board column
lossyClose Custom Fields on Leads, Contacts, and Opportunities map to typed columns in the corresponding Monday CRM board. Text fields become Text columns, date fields become Date columns, numeric fields become Number columns, and choice fields become Label or Status columns. We create the column in Monday before importing any records that reference it.
Close
Custom Activity
monday CRM
Separate board or sub-item structure
lossyClose Custom Activities require careful modelling in Monday because Monday does not support a Custom Activity Type concept. We design a separate board to represent the custom activity type or add sub-item structure to the relevant People/Deal board. The Custom Activity Type definition must be created in Monday before any activity records import; we handle this as a pre-import schema step. Any type-specific Custom Fields migrate as additional columns on the chosen structure.
Close
Custom Object
monday CRM
Separate board
lossyClose Custom Objects map to standalone boards in Monday that mirror the object schema. We create the board with columns matching each Custom Object field (by type), add any lookup relationships as Connect board columns or Link-to-item columns, and import the records as board items. Custom Object dependencies on standard objects (Lead, Contact, Opportunity) require the parent records to exist before the lookup reference can be resolved during import.
Close
User / Team Member
monday CRM
Workspace member
1:1Close Users map to Monday workspace members by email match. We extract every owner_id referenced on Lead, Contact, Opportunity, and Activity records and resolve against Monday workspace members during import. Any Close owner without a matching Monday member goes to a reconciliation queue for the customer's admin to provision before record import resumes.
| Close | monday CRM | Compatibility | |
|---|---|---|---|
| Lead | People item (CRM board)1:1 | Fully supported | |
| Contact | People item (CRM board)1:1 | Fully supported | |
| Opportunity | Deal item (CRM board)1:1 | Fully supported | |
| Pipeline | CRM board1:1 | Fully supported | |
| Pipeline Stage | Status column valuelossy | Fully supported | |
| Activity (Call, Email, SMS, Task) | Activity sub-items or column updates1:many | Fully supported | |
| Custom Field (Lead, Contact, Opportunity) | Board columnlossy | Fully supported | |
| Custom Activity | Separate board or sub-item structurelossy | Fully supported | |
| Custom Object | Separate boardlossy | Fully supported | |
| User / Team Member | Workspace member1:1 | 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.
Close gotchas
CSV exports drop all activity history silently
Smart Views can only export from the Leads tab
Workflows gatekept behind Growth and Scale plans
Custom Activities require strict dependency ordering
Rate limits enforced per endpoint group
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 scoping
We audit the Close account across tier (Solo/Essentials/Growth/Scale), active pipelines, Custom Fields per object, Custom Activity Types and type-scoped fields, Custom Objects, engagement volume, and active Workflows. We review any JSON export available and flag if only CSV exports have been used. The discovery output is a written migration scope covering record counts per object, pipeline structure, custom schema, and a list of active Workflows requiring rebuild documentation.
Monday board architecture design
We design the Monday CRM board structure to mirror the Close pipeline layout. This includes creating one CRM board per Close pipeline, configuring the default Deal_Value, Expected_Close, Owner, Person, and Status columns, adding custom columns mapped from Close Custom Fields, and setting Status column values to match Close's stage names and ordering. For Custom Activities and Custom Objects, we design the standalone board or sub-item structure before any data loads begin. Board design is validated in a Monday test workspace before production migration.
Data export and JSON validation
We request JSON exports from Close for all record types that carry activity history. We validate that activity arrays are present in the export (not truncated or empty) and flag any records where only CSV exports exist. We also extract Smart View filter criteria as named saved-search documentation for the customer's admin. Owner reconciliation begins here: we match every Close owner email against Monday workspace members and flag any gaps for the customer to provision before production migration.
Sandbox migration and reconciliation
We run a full migration into a Monday test workspace using production-like data volume. The customer's operations lead reconciles record counts (People items, Deal items, activity sub-items), spot-checks 20-40 random records against the Close source, and reviews the board structure and column mapping. Any mapping corrections, missing columns, or board configuration issues are resolved here. Sign-off on the sandbox migration gates the production migration start.
Production migration in dependency order
We run production migration in record-dependency order: workspace members validated, People items (Leads and Contacts) created with owner assignment resolved, CRM boards configured with Status values matching Close stages, Deal items created with pipeline and stage mapping resolved, activity sub-items (calls, emails, SMS, tasks) attached to the relevant People item, Custom Object boards created and populated, and Custom Activity records imported into their designed structure. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and Workflow rebuild handoff
We freeze Close writes during cutover, run a final delta migration of any records modified during the migration window, then enable Monday as the system of record. We deliver the Workflow and Sequence inventory document listing every active Close Workflow with its trigger, conditions, and actions, plus a recommended Monday Automation equivalent. We support a three-day hypercare window where we resolve any reconciliation issues. We do not rebuild Close Workflows as Monday Automations inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Close
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Close and monday CRM.
Object compatibility
2 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
Close: Per endpoint group with a lower limit on write operations; 429 response includes rate_reset value; limits enforced at the organisation level across all API keys.
Data volume sensitivity
Close 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 Close to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Close 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 Close
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.