Migrate your InTouch data
Conveyancing-focused legal CRM with strong automation templates and UK-centric workflow design, marketed at small-to-mid-sized property law firms managing high-volume transactions.
In its favor
Why people choose InTouch
The signal that keeps InTouch on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small law firms choose InTouch for its purpose-built conveyancing workflow templates that automate Land Registry tasks and client communication sequences without requiring custom development work.
The per-matter custom field architecture lets firms capture transaction-specific data points that standard CRM objects cannot represent, making the data model a direct fit for property law use cases.
InTouch's dedicated customer champion onboarding model appeals to firms with limited in-house IT resource who want a single named contact during the transition period.
Firms moving from legacy on-premise conveyancing systems cite InTouch's fully managed cloud infrastructure as a reason to migrate, removing hardware maintenance obligations entirely.
The platform's data export capability is built into all tiers including Standard, giving firms confidence they can retrieve their data if they need to leave the platform in future.
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.
Reasons to switch
Why people leave InTouch
The recurring reasons buyers give for replacing InTouch. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where InTouch fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
InTouch pricing overview
InTouch does not publish pricing on its website. All tiers require a sales conversation. The platform differentiates on export breadth, support tier, and backup options between Standard, Premium, and Enterprise, with New Starter and Platform occupying lower positions in the feature set.
New Starter
Tier 1 of 5
Not publicly listed — contact sales
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on InTouch's schedule — see our quote-based pricing →
What gets migrated
InTouch object support
Object-by-object support for InTouch migrations. Per-pair details surface during scoping.
Matters
Fully supportedMatters are the central work unit in InTouch, representing individual property transactions. We map matters 1:1 preserving the matter status, assigned fee-earner, key dates, and linked contacts. Custom field values are carried over as structured mappings rather than loose text fields.
Clients
Fully supportedClients are the primary parties on a matter. We migrate client records with full contact details, address history, and matter associations. Where the destination uses a Contact/Party object we split client records to the appropriate schema without losing the relationship to the originating matter.
Contacts
Fully supportedInTouch supports multiple contact types per matter including buyers, sellers, solicitors, and estate agents. We preserve contact type labels as custom properties in the destination so the relationship hierarchy remains legible after migration.
Matter Templates
Mapping requiredMatter templates define the stages, custom fields, and workflow tasks for each transaction type. We map template stage names to the destination's pipeline stages and flag any template-level custom fields that have no direct equivalent in the target system.
Custom Fields
Mapping requiredCustom fields are data markers tied to matter templates. They capture transaction-specific data throughout a deal. Migration requires a template pre-check to understand which custom fields exist and how they map to the destination schema.
Documents
Mapping requiredDocuments are linked to matters and stored in InTouch's document management system. We extract document metadata and file references. Document bodies can be migrated as binary file transfers if the destination supports document attachments.
Activities and Tasks
Mapping requiredActivities record workflow events and tasks against a matter. We sequence activities chronologically and map task status flags to the destination's equivalent activity or task object.
Users and Fee-Earners
Mapping requiredUser accounts map to fee-earners and admin roles. We preserve the user-to-matter assignment so that workload history and matter ownership transfer correctly to the destination system.
| Object | Support | Notes |
|---|---|---|
| Matters | Fully supported | Matters are the central work unit in InTouch, representing individual property transactions. We map matters 1:1 preserving the matter status, assigned fee-earner, key dates, and linked contacts. Custom field values are carried over as structured mappings rather than loose text fields. |
| Clients | Fully supported | Clients are the primary parties on a matter. We migrate client records with full contact details, address history, and matter associations. Where the destination uses a Contact/Party object we split client records to the appropriate schema without losing the relationship to the originating matter. |
| Contacts | Fully supported | InTouch supports multiple contact types per matter including buyers, sellers, solicitors, and estate agents. We preserve contact type labels as custom properties in the destination so the relationship hierarchy remains legible after migration. |
| Matter Templates | Mapping required | Matter templates define the stages, custom fields, and workflow tasks for each transaction type. We map template stage names to the destination's pipeline stages and flag any template-level custom fields that have no direct equivalent in the target system. |
| Custom Fields | Mapping required | Custom fields are data markers tied to matter templates. They capture transaction-specific data throughout a deal. Migration requires a template pre-check to understand which custom fields exist and how they map to the destination schema. |
| Documents | Mapping required | Documents are linked to matters and stored in InTouch's document management system. We extract document metadata and file references. Document bodies can be migrated as binary file transfers if the destination supports document attachments. |
| Activities and Tasks | Mapping required | Activities record workflow events and tasks against a matter. We sequence activities chronologically and map task status flags to the destination's equivalent activity or task object. |
| Users and Fee-Earners | Mapping required | User accounts map to fee-earners and admin roles. We preserve the user-to-matter assignment so that workload history and matter ownership transfer correctly to the destination system. |
Gotchas
What to watch for in InTouch migrations
Issues we've hit on past InTouch migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Custom fields are template-bound and require pre-migration schema review
Contact export runs asynchronously and can exceed one hour for large rolls
Legacy flash-era data may have inconsistent field encoding in exports
Matter export is not a self-service feature on all tiers
| Severity | Issue |
|---|---|
| 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 |
Leaving InTouch?
Where InTouch customers move next
12 destinations InTouch can migrate to.
How a InTouch migration works
Four steps, InTouch-specific
Connect
Not publicly documented for third-party migration use into InTouch. Scopes limited to read-only on the data we move.
Map
We translate InTouch-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate InTouch quirks before production.
Migrate
Full migration with InTouch rate-limit handling. Rollback available throughout.
FAQ
InTouch migration FAQ
Answers to the questions buyers ask most during InTouch migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your InTouch migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate InTouch.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your InTouch setup and destination — written quote back within a business day.