How long does an InTouch CRM to Monday.com CRM migration take?

Migrations under 10,000 Contacts, 2,000 Deals, and 100,000 Activity records typically complete in two to three weeks. Migrations with multiple InTouch pipelines, extensive custom field schemas, large activity histories exceeding 200,000 records, or complex Board structure decisions extend to five to eight weeks. Monday.com's API rate limits (40-250 concurrent requests depending on plan) govern write throughput during migration, and large activity batches require chunking with retry intervals that extend timelines beyond what a simple record count would suggest.

Do InTouch Workflows and automation rules migrate to Monday.com?

No. InTouch Workflows and automation rules do not migrate as code because Monday.com's automation recipe model (trigger-action pairs scoped to individual Boards) is structurally different from InTouch's CRM-wide workflow rules. We do not migrate automations. We deliver a written inventory of every active InTouch Workflow and automation rule with its trigger, conditions, actions, and a recommended Monday.com Automation equivalent, including which Board each automation should be configured on. Your admin rebuilds them in Monday.com's native automation builder post-migration. Lead scoring rules similarly do not migrate; we document the scoring criteria for manual recreation or replacement with Monday.com's native Insights features.

What does an InTouch CRM to Monday.com CRM migration typically cost?

Migrations under 10,000 Contacts, 2,000 Deals, and no complex custom field schemas land between $3,500 and $5,500. Migrations with multiple pipelines, extensive custom fields, large activity histories, or a parallel Work Management-to-CRM board structure transition move to $7,500-$11,000. Monday.com CRM subscription cost ($10-$32 per user per month) sits outside the migration fee and remains the customer's recurring cost. Monday.com does not charge a mandatory onboarding fee for CRM plans.

How do you handle InTouch custom fields in Monday.com?

InTouch Custom Fields map to Monday.com Column types matched by data type: text fields to Text columns, numbers to Number columns, dates to Date columns, dropdown selections to Dropdown columns, and true/false flags to Checkbox columns. InTouch custom field dependencies (conditional display rules) require manual recreation in Monday.com's Column dependency settings because the API-level dependency payload structure differs from InTouch's implementation. We document every InTouch custom field with its type, dependencies, and the recommended Monday.com Column configuration so your admin can set dependencies correctly post-migration.

Will our InTouch activity history (calls, emails, meetings, notes) appear in Monday.com?

Yes. We migrate InTouch Activity records as Updates on the corresponding Monday.com Items (Contacts, Companies, Deals). Each Update carries the timestamp, activity type, user attribution, and content body. Activity types are prefixed in the Update text ([Call], [Email], [Meeting], [Note]) for filtering in Monday.com's Activity log. Activity ordering is preserved by timestamp. Parent record resolution (which InTouch Contact or Deal owns this activity) is validated before each batch insert, and orphaned activities are flagged for manual review rather than silently dropped.

What happens to InTouch owner data in Monday.com?

InTouch Owner records map to Monday.com Team Members by email address match. During scoping, we extract every distinct owner email and cross-reference against the Monday.com destination account's member list. Owners without a matching Team Member enter a reconciliation queue for your admin to provision before migration resumes. InTouch owner attribution on Contacts, Companies, Deals, and Activities becomes the Assignee column value on the corresponding Monday.com Items, preserving sales rep accountability in the timeline.

Can we keep InTouch CRM for some teams while migrating sales to Monday.com CRM?

This is technically possible but not recommended as a long-term configuration because running two CRMs with overlapping data creates synchronization complexity and data divergence risk. If a partial migration is required (e.g., migrating one sales team while another continues on InTouch), we can scope the migration to specific InTouch Pipelines and owner groups, and configure Monday.com Boards accordingly. The customer must establish a sync strategy for shared contacts between the two systems. We do not provide ongoing sync or dual-write tooling as part of the standard migration scope.

How do we handle the structural difference between InTouch Pipelines and Monday.com Boards?

InTouch Pipelines are a Deal container with stages as properties; Monday.com uses Boards with Columns as field definitions and Column groups or Status Column values as stages. During scoping, we present three structural options: one Board per InTouch Pipeline with Status Column values for stages; one Board with Column groups per stage; or a single unified Board with a Status Column. The customer chooses the model based on their reporting and workflow preferences. We configure the chosen structure before any Deal data migrates. Changing the Board structure after migration requires re-import of affected records.

InTouch CRM to monday CRM Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from InTouch CRM to Monday.com CRM is a structural pivot from a traditional CRM record model to a board-based Item architecture. InTouch stores Contacts, Companies, Deals, and Activities within user-defined Pipelines; Monday.com CRM represents each record as an Item on a Board with Columns serving as field definitions. We extract InTouch's pipeline stages and map them to Monday.com Column groups, preserve InTouch custom field values as typed Monday columns (text, number, date, dropdown, checkbox), and resolve InTouch owner email references against Monday.com Team Members. Activity timestamps carry forward to maintain the sales history your team relies on. InTouch's CSV-based export model means we work with flat file extracts for Contacts and Deals, requiring deduplication and relationship resolution before Board population. Monday.com's API rate limits (40 concurrent requests on standard plans, 100 on Pro, 250 on Enterprise) govern write throughput during migration, and we implement batch chunking and exponential backoff to stay within those thresholds. Workflows, automations, and lead scoring rules in InTouch do not migrate as code; we deliver a written inventory of each for your admin to rebuild in Monday.com's native automation builder.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

InTouch CRM

What's pushing teams away

Limited advanced customization — Capterra UK reviewers cite the lack of flexible reporting, integrations, and dashboard customization as the main reason teams outgrow the platform.
Integration ecosystem is narrow compared to mainstream SMB CRMs (HubSpot, Pipedrive, Zoho), pushing teams with custom tech stacks to switch.
Reporting and analytics are basic, prompting data-driven teams to move to platforms with richer BI integration.
Small public review base (mostly Capterra UK) limits peer-reference signal, making procurement teams hesitant when scaling up.
No publicly documented bulk API restricts modern automation workflows, so power users hit the integration ceiling earlier than on platforms with open developer ecosystems.

Choosing

monday CRM

What's pulling them in

Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How InTouch CRM objects map to monday CRM

Each row shows how a InTouch 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.

InTouch CRM

Contact

maps to

monday CRM

Item (on People Board)

1:1

Fully supported

InTouch Contact records map to Monday.com CRM Item records on a dedicated People Board. First name, last name, email, phone, and address fields map to corresponding Monday.com column types (text, email, phone, location). We resolve the InTouch owner email against Monday.com Team Members to set the Item's Assignee column. Any Contact-level custom fields in InTouch map to additional Columns on the destination Board, preserving type (dropdown, number, date, checkbox). Duplicate email detection runs against the destination Board before insert to avoid creating duplicate Items.

InTouch CRM

Company

maps to

monday CRM

Item (on Organizations Board)

1:1

Fully supported

InTouch Company records map to Monday.com CRM Item records on the Organizations Board. Company name, domain, industry, employee count, and address map to typed Columns. The Organizations Board uses a Board Relation column to link each Company Item to related Contact Items on the People Board, maintaining the InTouch Company-to-Contact relationship. Company owner maps to the Assignee column.

InTouch CRM

Deal

maps to

monday CRM

Item (on Deals Board)

1:1

Fully supported

InTouch Deal records map to Monday.com CRM Item records on a Deals Board. The InTouch pipeline name becomes the Board name, and the InTouch pipeline stages become Column groups or status Column values on the Board. Deal name, amount, expected close date, and probability map to text, number, date, and percentage columns. The Board Relation column links each Deal Item to the associated Contact and Company Items, replicating InTouch's relationship model.

InTouch CRM

Pipeline

maps to

monday CRM

Board + Column Group

1:many

Fully supported

InTouch Pipelines (each containing Deals across multiple stages) map to separate Monday.com Boards, with the Pipeline name as the Board title. InTouch stage labels (e.g., Prospect, Qualified, Proposal, Negotiation, Won, Lost) become Column values in a status Column on the Board. If a single InTouch Pipeline needs to map to a single Board with Column groups representing stages, we configure it per the customer's preference during scoping. Both models preserve stage-level reporting capability.

InTouch CRM

Deal Stage

maps to

monday CRM

Status Column Value

lossy

Fully supported

InTouch Deal stage labels map to Monday.com Status Column values. We preserve the stage sequence order and color coding from InTouch where available, setting the corresponding color in Monday.com's Status Column. Stage probability percentages from InTouch do not map directly to Monday.com native fields but can be stored in a separate number column if reporting requires them.

InTouch CRM

Activity

maps to

monday CRM

Update (on Item)

1:1

Fully supported

InTouch Activity records (calls, emails, meetings, tasks, notes) map to Monday.com Item Updates. Each Update carries the timestamp, activity type, user attribution (from InTouch owner), and content body. Activity types are prefixed in the Update text (e.g., [Call], [Email], [Meeting]) for filtering. For InTouch Activities linked to a specific Deal or Contact, the Update attaches to the corresponding Item on the Deals or People Board. Activity history ordering is preserved by timestamp.

InTouch CRM

Custom Field

maps to

monday CRM

Column

lossy

Fully supported

InTouch Custom Fields defined on Contacts, Companies, or Deals map to Monday.com Column types matched by data type: text fields to Text columns, numbers to Number columns, dates to Date columns, dropdown selections to Dropdown columns, and true/false flags to Checkbox columns. InTouch Custom Fields with dependencies (conditional display rules) map to Monday.com Column dependencies where supported; otherwise, we document the dependency logic for manual recreation in Monday.com's Column settings.

InTouch CRM

Owner

maps to

monday CRM

Team Member

1:1

Fully supported

InTouch Owner records map to Monday.com Team Members by email address match. We extract every distinct owner email from InTouch Contacts, Companies, Deals, and Activities, then resolve against the Monday.com destination account's member list. Owners without a matching Team Member enter a reconciliation queue for the customer's admin to provision before migration resumes. The Owner name populates the Assignee column on migrated Items.

InTouch CRM	monday CRM	Compatibility
Contact	Item (on People Board)1:1	Fully supported
Company	Item (on Organizations Board)1:1	Fully supported
Deal	Item (on Deals Board)1:1	Fully supported
Pipeline	Board + Column Group1:many	Fully supported
Deal Stage	Status Column Valuelossy	Fully supported
Activity	Update (on Item)1:1	Fully supported
Custom Field	Columnlossy	Fully supported
Owner	Team Member1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

InTouch CRM gotchas

High

CSV-based import is the primary documented data path

Medium

Stage and pipeline label drift across customer instances

Medium

Limited custom-object surface

Low

All-in-one bundling means multiple modules' data must be reconciled

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

InTouch CRM gotchas		monday CRM gotchas
Severity	Issue	Severity	Issue
High	CSV-based import is the primary documented data path	High	Subitems are not included in bulk exports
Medium	Stage and pipeline label drift across customer instances	High	Daily API call limits vary sharply by plan
Medium	Limited custom-object surface	Medium	Legacy automations (Sentence Builder) are being deprecated
Low	All-in-one bundling means multiple modules' data must be reconciled	Medium	Excel and account exports only include table views
		Low	Enterprise admins can disable non-admin exports

Pair-specific challenges

Monday.com API rate limits constrain batch write throughput

Monday.com enforces concurrency limits of 40 concurrent requests on standard plans, 100 on Pro, and 250 on Enterprise. Additionally, the IP limit caps individual IP addresses at 5,000 requests per 10 seconds, and daily call limits apply per account. InTouch CRM exports produce CSV files that require parsing, transformation, and API inserts. Without batch chunking and exponential backoff against Monday.com's error responses (IP_RATE_LIMIT_EXCEEDED, RESOURCE_PROTECTION_LIMIT), large migrations will hit throttling errors and stall. We chunk inserts into batches of 50-100 records per request, implement retry logic with increasing backoff intervals, and monitor retry-after headers to stay within limits.
InTouch custom field dependencies have no direct Monday.com equivalent

InTouch allows custom fields to have conditional display rules (field A must be populated before field B becomes visible). Monday.com supports Column dependencies in its recipe and custom field infrastructure, but these are non-nullable and require specific payload handling during API calls. We audit InTouch's custom field dependency chains during scoping and either recreate them as Monday.com Column dependencies or document them for manual configuration post-migration. Fields without dependencies map directly to equivalent Monday.com column types without additional configuration.
InTouch activity history requires relationship resolution before migration

InTouch Activities are linked to Contacts or Deals by internal ID, not by email or name. Monday.com Updates attach to Item IDs. We must resolve InTouch activity-parent relationships (which Contact or Deal ID owns this activity) before writing Updates to the correct Items in Monday.com. If the parent Contact or Deal fails to migrate or is deduplicated during import, the activity orphan must be either attached to a fallback Item or flagged for manual review. We run relationship validation after each batch and emit a reconciliation report before proceeding.
Monday.com does not migrate InTouch workflows, automations, or lead scoring as code

InTouch Workflows and automation rules (property-triggered actions, time-based follow-ups, lead scoring updates) have no direct Monday.com equivalent in the migration payload. Monday.com's automation recipes use trigger-action pairs scoped to individual Boards, which is a different model from InTouch's CRM-wide automation rules. We do not migrate automations as code. We deliver a written inventory of every active InTouch Workflow with its trigger, conditions, actions, and recommended Monday.com Automation equivalent, including which Board each automation should be configured on. The customer's admin rebuilds them in Monday.com's native automation builder post-migration.
Monday.com requires board structure decisions before data migration begins

InTouch stores Deals within a Pipeline; Monday.com CRM requires you to decide how to represent that structure. Options include a single Board with Column groups per stage, multiple Boards per pipeline, or a single Board with a Status Column. The choice affects how reporting, filtering, and automation triggers work in Monday.com. We present these options during scoping, the customer makes the structural decision, and we configure the Board before any Deal data moves. Changing the Board structure after data migration requires re-import of affected records.

Migration approach

Six steps for a successful InTouch CRM to monday CRM data migration

Discovery and export preparation

We audit the InTouch CRM account for record counts across Contacts, Companies, Deals, and Activities; count of active Pipelines and their stage labels; custom field definitions and their types; owner list and email addresses; and any active Workflow or automation rules. We coordinate with the customer's InTouch admin to generate CSV exports of each object type. If the InTouch export produces incomplete relationships (e.g., Activity records without resolved parent Contact ID), we request supplemental exports or manual relationship mapping from the admin. The discovery output is a written migration scope with record counts, pipeline mapping decisions, and custom field inventory.
Monday.com board design and column configuration

We configure Monday.com Boards before any data import. The People Board holds migrated Contacts with typed columns matching InTouch field names and types. The Organizations Board holds migrated Companies with Board Relation columns linking to People Board Items. Each InTouch Pipeline becomes a Deals Board with Status Columns matching the pipeline stages. We create Column types for all InTouch custom fields, set up Board Relations for Contact-Company-Deal linking, and configure Team Member accounts matching the InTouch owner list. Board design is validated in a Monday.com test workspace before production migration begins.
Owner reconciliation and Team Member mapping

We extract every distinct InTouch Owner email and match against Monday.com Team Members in the destination account. Owners without a matching Team Member go to a reconciliation queue for the customer's admin to provision. Monday.com Guest accounts can serve as a fallback for inactive InTouch owners if the customer wants to preserve attribution without provisioning a full seat. Migration cannot proceed to Contact and Deal imports until the owner mapping is resolved because Assignee columns on Items require a valid Team Member reference.
Contact and Company migration with deduplication

We run Contact migration first, inserting Items into the People Board with email address as the deduplication key. If a Contact email already exists in Monday.com (from prior manual entry or a prior migration attempt), we flag it for the customer's admin to decide whether to update or skip. Company migration follows, with Board Relations linked to the resolved Contact Items. Both phases emit row-count reconciliation reports comparing InTouch export counts to Monday.com insert counts.
Deal migration with pipeline-stage mapping

We migrate Deals after Contacts and Companies are confirmed in Monday.com so that Board Relations can resolve correctly. Each Deal Item is linked to its associated Contact and Company Items via Board Relation columns. The Status Column on the Deals Board is set to the InTouch Deal stage label. Activity history (Updates) attaches to Deal Items with timestamps preserved. We chunk Deal inserts in batches of 50-100 and implement retry logic against Monday.com API rate limit responses. A delta migration captures any Deals modified during the active migration window.
Activity history migration and cutover

We migrate InTouch Activity records as Updates on the corresponding Monday.com Items, resolving parent IDs against the migrated Contact, Company, and Deal Items. Activity types are prefixed in Update text for filtering. We apply rate-limit handling with exponential backoff across the activity batch. During cutover, we freeze InTouch write access for the migration window, run a final delta migration of any records modified since the initial extract, then hand off Monday.com as the system of record. We deliver the Workflow and automation inventory document for the customer's admin to rebuild in Monday.com's native automation builder.

Platform deep dives

Context on both ends of the pair

InTouch CRM

Source

Strengths

All-in-one bundling of CRM, email marketing, direct mail, SMS, surveys, contact management, and task tracking in one platform
Strong fit for UK small businesses — Capterra UK reviewers consistently highlight ease of use and customer support
Flat per-user pricing keeps costs predictable as small teams grow
Automation features for email marketing, task tracking, and customer segmentation work out of the box
Email-to-CRM workflow described as seamless by users, useful for marketing-led small businesses

Weaknesses

Limited advanced customization options for reporting, dashboards, and integrations
No publicly indexed bulk API or developer portal
Small public review footprint outside Capterra UK
Custom objects beyond standard CRM entities are not supported
Vendor's UK focus may not suit US/international teams expecting global feature parity

monday CRM

Destination

Strengths

Board-based UI makes pipeline stages and deal progress visually obvious without training.
No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
Flexible column system supports custom CRM fields without schema changes or admin involvement.
Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

	InTouch CRM Source	monday CRM Destination
Strengths	All-in-one bundling of CRM, email marketing, direct mail, SMS, surveys, contact management, and task tracking in one platform Strong fit for UK small businesses — Capterra UK reviewers consistently highlight ease of use and customer support Flat per-user pricing keeps costs predictable as small teams grow Automation features for email marketing, task tracking, and customer segmentation work out of the box Email-to-CRM workflow described as seamless by users, useful for marketing-led small businesses	Board-based UI makes pipeline stages and deal progress visually obvious without training. No-code automation builder requires no developer resources to create lead routing and stage-triggered actions. Flexible column system supports custom CRM fields without schema changes or admin involvement. Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead. Layered product means teams already on monday Work Management can add CRM without migrating existing data.
Weaknesses	Limited advanced customization options for reporting, dashboards, and integrations No publicly indexed bulk API or developer portal Small public review footprint outside Capterra UK Custom objects beyond standard CRM entities are not supported Vendor's UK focus may not suit US/international teams expecting global feature parity	No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature. Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward. Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated. Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers. Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Moderate CRM migration. 1 of 8 objects need a manual workaround.

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across InTouch CRM and monday CRM.

Object compatibility
D
1 of 8 objects need a manual workaround.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
InTouch CRM: Not publicly documented.
Data volume sensitivity
B
InTouch CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from InTouch CRM to monday CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

InTouch CRM

monday CRM

How InTouch CRM objects map to monday CRM

What specifically takes care here

Six steps for a successful InTouch CRM to monday CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your InTouch CRM to monday CRM migration cost

What are you migrating?

Frequently asked questions about InTouch CRM to monday CRM data migrations

Can't find your answer?

Related migrations to explore

Move from InTouch CRM.
Land in monday CRM, intact.

Migrate from InTouch CRM to monday CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

InTouch CRM

monday CRM

How InTouch CRM objects map to monday CRM

What specifically takes care here

Six steps for a successful InTouch CRM to monday CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your InTouch CRM to monday CRM migration cost

Frequently asked questions about InTouch CRM to monday CRM data migrations

Can't find your answer?

How long does an InTouch CRM to Monday.com CRM migration take?

Do InTouch Workflows and automation rules migrate to Monday.com?

What does an InTouch CRM to Monday.com CRM migration typically cost?

How do you handle InTouch custom fields in Monday.com?

Will our InTouch activity history (calls, emails, meetings, notes) appear in Monday.com?

What happens to InTouch owner data in Monday.com?

Can we keep InTouch CRM for some teams while migrating sales to Monday.com CRM?

How do we handle the structural difference between InTouch Pipelines and Monday.com Boards?

Related migrations to explore

Move from InTouch CRM. Land in monday CRM, intact.

Move from InTouch CRM.
Land in monday CRM, intact.