CRM migration

Migrate from InTouch to monday CRM

Field-level mapping, validation, and rollback between InTouch and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

InTouch logo

InTouch

Source

monday CRM

Destination

monday CRM logo

Compatibility

100%

11 of 11

objects map 1:1 between InTouch and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

InTouch CRM stores data in a conventional object-relational model: contacts, companies, deals, and custom fields with relationships managed through foreign keys. Monday CRM uses a board-and-item schema where every CRM entity — People, Organizations, Opportunities, Activities — lives as an Item on a Board, with column types replacing standard fields. This structural difference is the core challenge: InTouch's contact record has discrete firstname, lastname, email, and company fields; Monday Person items map those to First Name, Last Name, Email, and the person column respectively. InTouch's deal pipeline stages are pick-list values stored on the deal object; Monday's Opportunity pipeline uses a Status column with colored labels as stage proxies. We map InTouch contacts to Monday People, companies to Organizations, and deals to Opportunity items on dedicated pipeline boards. Custom fields in InTouch become custom columns in Monday, with type inference applied (text, number, date, dropdown). InTouch automations and workflows — reported as a top frustration by InTouch users who cited limited flexibility — do not transfer and must be rebuilt as Monday Recipe automations after migration. Activity history (calls, emails, notes) migrates as Item updates. Files are re-uploaded to Monday's file storage. The migration uses Monday's REST API (rate-limited per plan: 1,000 calls/day on Basic, 10,000 on Pro, 25,000 on Enterprise) and bulk-item creation where column types are compatible. A 24–48 hour delta-pickup window captures in-flight records during cutover.

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 logo

InTouch

What's pushing teams away

  • Advanced customisation for dashboards, reporting, and workflow branching is limited, causing firms with complex or non-standard transaction types to outgrow the platform's flexibility.
  • The mobile app receives consistent criticism for poor usability and feature gaps compared to the desktop interface, which frustrates fee-earners who work on-site at properties.
  • The transition from the legacy flash-based version to the modern platform disrupted established users' workflows, and some firms report the learning curve on the new UI was steeper than expected.
  • Firms requiring deep third-party integrations with accounting software, Land Registry portals, or practice management suites find InTouch's native integration ecosystem too narrow for their needs.

Choosing

monday CRM logo

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 objects map to monday CRM

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

Contact

maps to

monday CRM

People Item (Monday CRM Person)

1:1
Fully supported

InTouch contacts migrate as Monday Person items. The Person item type is a built-in Monday CRM entity that stores name, email, phone, and social links. First name, last name, email, and phone map directly to Monday Person fields. The primary company association maps to the Organization item linked via Monday's organization-person relationship. Contact owner maps to the Owner person column, resolved by email match against Monday workspace members.

InTouch

Company

maps to

monday CRM

Organization Item (Monday CRM Organization)

1:1
Fully supported

InTouch companies migrate as Monday Organization items, the CRM-native entity for business records. Organization name, domain, industry, employee count, and address fields map to corresponding Organization item columns. Parent-company hierarchies in InTouch translate to Monday's organization sub-organization structure. Multi-company contacts (N:N in InTouch) are surfaced as primary-company links on the Person item, with secondary company associations noted as a custom text column.

InTouch

Deal

maps to

monday CRM

Opportunity Item (Pipeline Board)

1:1
Fully supported

InTouch deals map to Monday Opportunity items on a dedicated CRM pipeline board. Each InTouch deal pipeline becomes one Monday board with a Status column representing pipeline stages. Deal fields (name, value, stage, close date, owner) map to Opportunity item columns. The deal stage in InTouch (e.g., Prospecting, Proposal, Negotiation) becomes a Status column label in Monday's pipeline view, preserving stage order for visual kanban display.

InTouch

Custom Field

maps to

monday CRM

Custom Column (Board Column)

1:1
Fully supported

InTouch custom fields defined per-matter templates become Monday custom columns. FlitStack infers column type from InTouch field type: text fields become Text columns, numbers become Numbers columns, dates become Date columns, and pick-list fields become Dropdown columns. For fields with no Monday equivalent (e.g., complex data types), a Text column stores the serialized value for reference. Type inference is verified against Monday's supported column types before migration.

InTouch

Activity (Call, Email, Meeting, Note)

maps to

monday CRM

Item Updates (Monday Activity)

1:1
Fully supported

InTouch activity logs (calls logged, emails sent/received, meetings, notes) migrate as Updates on the corresponding Monday Person or Opportunity item. Each activity becomes a timestamped update with the activity type, summary, and owner noted in the update body. Original timestamps and owner names are preserved in the update text. This gives Monday users a full activity timeline inside the item without requiring a separate activity object.

InTouch

Attachment / File

maps to

monday CRM

Monday Files (File Column or Update Attachment)

1:1
Fully supported

InTouch file attachments stored on contacts, companies, or deals are downloaded and re-uploaded to Monday's file storage. Files attach to the corresponding Item via a File column or as update attachments. Monday's file storage limits apply: files upload to monday.com's cloud storage; inline images in InTouch notes are extracted and rehosted. Large file batches are uploaded in sequence to avoid Monday's concurrency limits.

InTouch

User / Owner

maps to

monday CRM

Workspace Member (Monday Person Column)

1:1
Fully supported

InTouch users and deal owners are matched against Monday workspace members by email address. Unmatched owners are flagged before migration: your team either provisions them as Monday workspace members or assigns their InTouch records to a fallback owner. This ensures every migrated item has a valid Owner person column in Monday rather than a null assignment.

InTouch

Tag / Label

maps to

monday CRM

Tag Column (Monday Tags)

1:1
Fully supported

InTouch contact tags and deal labels migrate as Monday Tags on the Person or Opportunity item. Tags are a native column type in Monday CRM, supporting multi-select tag application. This preserves your categorization logic without requiring a custom field. Tags are mapped verbatim; if tag names conflict with Monday reserved keywords, FlitStack applies a prefix (IT_) to the tag name.

InTouch

Pipeline

maps to

monday CRM

Pipeline Board (Monday CRM Board)

1:1
Fully supported

Each InTouch deal pipeline maps to one Monday CRM board with the Pipeline view enabled. Monday's Pipeline view presents Opportunity items grouped by the Status column, which represents pipeline stages. You can configure multiple pipelines in Monday (one board per pipeline) or consolidate multiple InTouch pipelines into a single board using a Pipeline Name column to differentiate them.

InTouch

InTouch Workflow / Automation

maps to

monday CRM

N/A (not migrated)

1:1
Fully supported

InTouch automations and workflow rules — including lead routing, stage-change triggers, and email follow-up sequences — are not migratable to Monday. Monday uses Recipe-based automations scoped to board columns, which have a different trigger model. FlitStack exports your InTouch workflow definitions as a reference document your Monday admin can use to rebuild equivalent automations using Monday's Recipe builder or integrations with Zapier/Make.

InTouch

Email Template / Sequence

maps to

monday CRM

N/A (not migrated)

1:1
Fully supported

InTouch email templates and drip sequences do not migrate to Monday CRM. Monday does not have a native email template or sequence system in the CRM module; email templates are typically handled through integrations (e.g., Gmail sync, Outlook integration, or third-party tools). We export your InTouch templates as HTML files for reference and note that Monday's Smart Templates feature covers basic templating at the item level.

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 logo

InTouch gotchas

High

Custom fields are template-bound and require pre-migration schema review

Medium

Contact export runs asynchronously and can exceed one hour for large rolls

Medium

Legacy flash-era data may have inconsistent field encoding in exports

Low

Matter export is not a self-service feature on all tiers

monday CRM logo

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

Pair-specific challenges

  • InTouch automations do not transfer to Monday Recipe automations

    InTouch users who depend on automated lead routing, stage-change triggers, or drip sequences will find that these rules have no Monday equivalent that can be imported. Monday's Recipe automations are structured as condition-action pairs scoped to board columns and require manual recreation. The trigger models differ fundamentally: InTouch automations evaluate CRM object field changes, while Monday Recipes evaluate column value changes. FlitStack exports your InTouch automation definitions as a structured reference document listing each rule's trigger, conditions, and actions so your Monday admin can rebuild them in the Recipe builder. This is a migration gap that must be budgeted as post-migration admin work.

  • Monday's API rate limits can block large-record migrations on Basic plans

    Monday enforces plan-tiered API call limits: 1,000 calls per day on Basic, 10,000 on Pro, and 25,000 on Enterprise. For migrations exceeding 10,000 total records with attachments and activity updates, the daily call volume during migration can exceed the Basic plan limit. When DAILY_LIMIT_EXCEEDED fires, the migration pauses until midnight UTC when the limit resets. For large InTouch datasets migrating to Monday Basic, FlitStack uses batched item creation with exponential backoff and pre-coordinates migration windows to avoid limit collisions. We recommend migrating to a Monday Pro account for datasets over 5,000 records to avoid throttling delays.

  • Board-and-item architecture means no standard CRM opportunity-contact role model

    InTouch supports N:N relationships between contacts and deals natively through relationship tables. Monday's Opportunity items link to Person items via a single-person Owner column and an optional secondary Person column, but there is no built-in Contact Role model equivalent to Salesforce's Opportunity Contact Roles. Teams that track which contacts are involved in a deal (e.g., Decision Maker, Influencer, Economic Buyer) cannot model this natively in Monday's standard Opportunity board. FlitStack surfaces this as a mapping gap: non-primary contact associations can be stored in a Text column listing contact names and roles, or a separate linking board can be created to track multi-contact deal involvement.

  • Monday's per-seat pricing can surprise teams migrating from InTouch's tiered model

    InTouch pricing tiers gate features (SMS, advanced email, custom fields) at the plan level. Monday CRM uses flat per-seat pricing (Basic $12/seat/month, Standard $17, Pro $28) with automation action-count limits per tier. Teams accustomed to InTouch's feature-gated model may not anticipate that Monday's automation limits (250 actions/month on Standard, 25,000 on Pro) can be reached quickly by teams with high-volume automations. Additionally, Monday has a minimum 3-seat requirement on paid plans. FlitStack includes a pricing impact analysis in the migration plan that compares your current InTouch seat count and feature tier against Monday's per-seat model so you can choose the right Monday plan before migration begins.

  • Monday's column type rigidity means complex InTouch field types require flattening

    InTouch custom fields support mixed-type data including date-time combinations, multi-select arrays, and freeform rich text. Monday board columns each have a single enforced type — a Date column stores dates only, a Numbers column stores numbers only, a Text column stores plain text. Fields with complex composite data in InTouch (e.g., a custom field storing 'contact_rating + date of last contact + notes' in a single field) must be decomposed into separate Monday columns. FlitStack's field profiling phase identifies composite InTouch custom fields before migration and creates a flattening plan mapping each component to a separate Monday column, with the original value preserved in a Reference Text column.

Migration approach

Six steps for a successful InTouch to monday CRM data migration

  1. Profile InTouch data and design Monday board structure

    FlitStack AI connects to InTouch via API or CSV export and inventories all contacts, companies, deals, custom fields, activity logs, and files. We identify data quality issues (duplicate contacts, orphaned deals, null owner fields) and flag them for cleanup. Simultaneously, we design the Monday CRM workspace: a People board for contacts, an Organizations board for companies, and one pipeline board per InTouch deal pipeline with Status columns configured to match InTouch stage names. We also identify which Monday plan your team needs based on record volume and automation requirements.

  2. Create Monday columns and user accounts

    Before importing data, FlitStack provisions the Monday column structure: standard Person, Organization, and Opportunity columns are created, and custom InTouch fields are mapped to Monday column types (Text, Numbers, Date, Dropdown, Tags, etc.). Owner columns are set up to reference Monday workspace members. We also resolve InTouch owner emails against Monday workspace members — unmatched owners are flagged and your team provisions Monday accounts or assigns a fallback owner before the import step runs.

  3. Migrate organizations, then people, then opportunities

    Monday's data model requires Organizations to exist before Persons can link to them, and both to exist before Opportunities can link to contacts and companies. FlitStack sequences the migration: Organizations (companies) load first, then People (contacts) with their Organization links, then Opportunities (deals) with their Person links and Organization links. This order ensures foreign-key relationships resolve correctly in Monday. Activity logs (calls, emails, meetings, notes) are written as Item Updates on the corresponding Person or Opportunity item after the parent record exists.

  4. Run a sample migration with field-level diff

    A representative slice of 100–500 records migrates first — spanning contacts, companies, deals, and activity updates. FlitStack generates a field-level diff between the InTouch source values and the Monday destination values so you can verify column mapping accuracy, Status column stage labels, owner resolution, and organization-person link integrity before the full run. You review the diff and approve or adjust mappings before we commit to the full migration.

  5. Cut over with delta-pickup for in-flight records

    The full migration runs against Monday, loading all remaining records in the sequenced order. A delta-pickup window (24–48 hours) captures any InTouch records created or modified during the cutover period so Monday reflects the final state at go-live. Monday's API rate limits are managed with batched requests and backoff logic. Audit log captures every operation. One-click rollback is available if reconciliation fails — we revert the Monday workspace to its pre-migration state and re-run with corrected mappings.

Platform deep dives

Context on both ends of the pair

InTouch logo

InTouch

Source

Strengths

  • Purpose-built conveyancing workflow templates with Land Registry task automation built in.
  • Fully managed cloud infrastructure with six file replicas across two regions and real-time database replication.
  • Data export capability included at all pricing tiers, not gated behind Enterprise only.
  • Dedicated customer champion and structured onboarding for firms with limited in-house IT capacity.
  • 2FA security enforced for both users and clients accessing the system.

Weaknesses

  • Advanced customisation for dashboards, reports, and workflow branching is limited compared to general-purpose legal platforms.
  • Mobile app is widely reported as under-featured and difficult to use on-site.
  • Native integration ecosystem with third-party accounting, Land Registry, and practice management tools is narrow.
  • Transition from the legacy flash-based interface created workflow disruption for established users that some firms still reference negatively.
monday CRM logo

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.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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: Not publicly documented.

  • Data volume sensitivity

    B

    InTouch doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your InTouch to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about InTouch to monday CRM data migrations

Answers to the questions buyers ask most during InTouch to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your InTouch to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most InTouch-to-Monday migrations complete within 48–72 hours for under 25,000 total records. Larger setups with 25,000+ records, multiple pipeline boards, or extensive custom fields extend to 7–14 days. The longest planning step is designing the Monday board structure and mapping InTouch custom fields to Monday column types before data moves. Monday API rate limits on lower-tier plans (Basic: 1,000 calls/day) can extend timeline for very large datasets; migrating to a Pro plan during the migration window avoids throttling delays.

Adjacent paths

Related migrations to explore

Ready when you are

Move from InTouch.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day