Data migration route
Intapp to Lawmatics migration
Intapp is a cloud specialist tool, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.
IntappCloud- Matters: Carried across
- Contacts: Carried across
- Tasks: Carried across
- Intake: Carried across
- Documents: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Templates: Confirmed in the analysis
LawmaticsCloud- 4 carried
- 4 mapped
- 4 to confirm
What moves
What moves from Intapp to Lawmatics
Each row is a kind of record Intapp holds, whether Lawmatics has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNew business requests and their approvals, by client and matter. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient, engagement and relationship data in Conflicts and DealCloud. | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partClient guideline documents and vendor agreements in Intapp Terms. | Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import. | Carried with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails reach a matter through mail sync from a connected mailbox. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeNotes on matters, contacts and companies. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeAppointments, called events, with types and locations. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partApproval workflows, tasks and alerts tied to intake and client terms. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldIntapp Time captures time across devices. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partBillstream manages proforma review and approval. | Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldIntake request forms and workflows are built by each firm. | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntapp Intake runs client and matter onboarding; DealCloud holds pipeline. | Has a placePipelines and stages, marketing sources and campaigns. | Carried across |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against Intapp.
- Carried with mapping
- Lawmatics holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
People and history move. Files and accounts stay.
A CRM wants to know who the firm knows and what has passed between them. From Intapp that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.
A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in Intapp or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Intapp depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Intapp is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving Intapp
Nobody moves off Intapp as a whole. A firm replaces one product, or changes its practice system and finds that the Intapp products were fed by it. Either way the work starts by listing which products are licensed, what each holds that exists nowhere else, and which records are only copies of data owned by the finance system.
Name the product first
Intake, Conflicts, Walls, Terms, Time, Billstream and DealCloud each keep different records. A plan to move from Intapp means little until the product is named. The analysis opens with the list of products in use and whether each is on Intapp’s cloud or an earlier installation in the firm’s own environment.
Intake history
The Intake product holds each new business request with its answers, risk assessment and approvals. That is the firm’s evidence that a matter was opened properly. A practice system may take the client and matter but has no place for the approval trail, which is then kept as a document on the matter or in an archive.
Conflict search records
Conflicts brings client, engagement and relationship data together for searching and records the clearance of each search. The underlying names come from other systems and move with them. Clearance records do not, and the firm’s risk team decides how long it must stay retrievable and in what form.
Time before it is posted
The Time product captures time on phones and desktops and hands entries to the billing system. Entries still in draft, or captured but not released, may exist nowhere else. A cut-off is agreed so every timekeeper releases their time before the switch, and a count of unreleased entries is taken on the day.
Walls and who sees what
Walls sets information barriers once and enforces them across the firm’s other systems. When one of those systems is replaced, the restrictions have to be applied to the new one before any matter is opened to staff. The list of walled matters and their permitted teams is taken out early for that reason.
Where it is going
Arriving in Lawmatics
Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.
Contacts and matters load separately
The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.
Set up before loading
Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.
Statuses and matter numbers
Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.
Duplicates are matched by email
With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.
What has no place
There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Intapp holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Intapp, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Lawmatics as a trial and checked against Intapp: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Intapp are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Intapp as at the cutover date. Intapp is kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Intapp and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Intapp holds
What is in it, how its records link, and where each piece would sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Setting up Lawmatics
Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.
In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.
Set-up decisions in Lawmatics
- Pipelines and stages for intake and for open matters
- Practice areas, sub-statuses, relationship types and the matter numbering pattern
- Custom fields on matters, contacts and companies
- Intake forms, booking links and e-signature document templates
- Follow-up automations, with marketing sources and campaigns
- Mail and calendar sync, user roles and practice system integration
Questions
Intapp to Lawmatics: what firms ask
We are changing practice management system. What happens to our Intapp products?
They stay, but their connections change. Intake, Conflicts and Time work from the clients, matters and timekeepers in the practice system and write back to it. Each of those feeds is rebuilt against the new system and tested during the trial load, so new matters and time entries have a working route before go-live.
Can Intapp Time entries be moved into a practice system?
Released time normally already sits in the firm’s billing system, so it moves with that system. What needs attention is time still held in the capture tool. Timekeepers release it before the cut-off, and anything left is exported and loaded as unbilled entries against the right matters.
Is DealCloud covered?
DealCloud is Intapp’s relationship management product, used for contacts, pipeline and marketing. Moving it is a CRM migration in its own right. Contacts and their history are mapped to the new CRM or to the practice system’s contact records, and duplicates between the two lists are merged where they can be identified.
Does billing history from Intapp move into Lawmatics?
In part. Invoices and payments; a past invoice is entered as sent, then marked paid. Open items are matched to what Lawmatics can hold, and the rest of the billing history is kept as reports that open without Intapp.
Does everything in Intapp have a place in Lawmatics?
Most of it does on paper. Emails, notes, calendar entries and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Lawmatics is kept as a readable archive, and you see which before the move.
What has to be decided before Intapp data is loaded into Lawmatics?
Documents, time entries, billing records and custom fields are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries and templates are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Intapp and into Lawmatics
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Intapp and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from Intapp to Lawmatics?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.