Data migration route
Intapp to Filevine migration
Intapp is a cloud specialist tool, and Filevine is a cloud case management system. The records line up case for case, and the detail is in the fields and stages.
IntappCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Intake: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Templates: Confirmed in the analysis
FilevineCloud- 4 carried
- 4 mapped
- 4 to confirm
What moves
What moves from Intapp to Filevine
Each row is a kind of record Intapp holds, whether Filevine 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 as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient, engagement and relationship data in Conflicts and DealCloud. | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partClient guideline documents and vendor agreements in Intapp Terms. | Has a placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld in the activity feed of the project. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeDeadlines and calendar events. | 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 partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partBillstream manages proforma review and approval. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldIntake request forms and workflows are built by each firm. | Has a placeCustom sections and fields per project type. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntapp Intake runs client and matter onboarding; DealCloud holds pipeline. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Intapp.
- Carried with mapping
- Filevine 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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Intapp and Filevine may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Filevine, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
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 Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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 Filevine. 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 Filevine 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 Filevine 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Intapp to Filevine: 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 Filevine?
In part. Needs the Billing product enabled. Open items are matched to what Filevine 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 Filevine?
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 Filevine is kept as a readable archive, and you see which before the move.
What has to be decided before Intapp data is loaded into Filevine?
Time entries, billing records, custom fields and intake records 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 Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Intapp to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.