Data migration route
Time Matters to Filevine migration
Time Matters is a server-based practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Time MattersServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
- Intake: Confirmed in the analysis
FilevineCloud- 7 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Time Matters to Filevine
Each row is a kind of record Time Matters holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocuments are created, searched and tied to clients and matters. | Has a placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails and attachments are managed against matters. | Has a placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes and phone calls are separate records. | Has a placeHeld as notes in the activity feed. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCalled Events. | Has a placeDeadlines and calendar events. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldCalled ToDos. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partBasic billing; advanced billing in the Billing Matters edition. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldForms, fields and record layouts are set by the firm. | Has a placeCustom sections and fields per project type. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldMerge Templates, AutoEntry Forms, Triggers and Chains. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Confirmed in the analysis |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Time Matters.
- 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Time Matters has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Time Matters, and kept as the record of what was billed and held.
Time Matters runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Filevine is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Time Matters
Firms that have used Time Matters for years have usually reshaped it, and that is what takes thought when leaving. The standard records, which are contacts, matters, events, to-dos, notes, phone calls, emails and documents, move in a predictable way. What differs in every installation is the firm’s own forms, added fields, Triggers and Chains, and the analysis spends most of its time there.
Forms the firm redesigned
Record forms, field labels and layouts can be changed by the firm. A field that the default form calls one thing may carry a different label, and a different meaning, on the firm’s version. The mapping is made from the firm’s own form definitions, never from the default names.
Triggers and Chains
Triggers start tasks or events when a date or status changes, and Chains join steps into a sequence. AutoEntry Forms cut down repeated entry. The records they created come across, but the rules do not, so the processes that still matter are written down with the staff who use them and rebuilt in the destination.
Every record type is separate
Events, ToDos, phone calls, notes, emails and documents are distinct kinds of record, each tied to a matter or contact. Phone records in particular have no equivalent in many systems, and are loaded as dated notes. Counts for each record type are checked against Time Matters matter by matter.
Billing may be elsewhere
Time and expenses are recorded here, but invoices and ledgers may be kept in PCLaw or QuickBooks through a link, or in Billing Matters. The move identifies which, and treats that program as a second source. Matters are paired across the two using the reference the link relies on.
Supported versions turn over
The vendor retires versions on a published schedule, release by release, so a firm that has not upgraded for a few years may be on one that is out of support. It can still be moved. Its backup is checked early, since vendor help with a failed restore may not be on offer for a retired release.
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 Time Matters 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 Time Matters, 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 Time Matters: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Time Matters 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 Time Matters as at the cutover date. Time Matters 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 Time Matters 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 Time Matters 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
Time Matters to Filevine: what firms ask
Do our documents come across with their matter links?
Each document in Time Matters has a record that ties it to a client or matter. The record supplies the matter, description and date, and the file supplies the content. Both are needed. Where a record refers to a file that has been moved or deleted, it is reported before the trial load.
Can we keep our custom fields?
The ones in use, yes, if the destination has custom fields for matters and contacts. Every field the firm added is listed in the analysis with how often it is filled. Fields that held structured data move as fields. Those used as scratch space usually become part of a note, by the firm’s choice.
We link Time Matters to PCLaw. Do they move together?
They should be planned together even if they go live a few days apart. The link keeps clients, matters and time in step between the two, and both feed the new system. One matter list is built from both, with PCLaw as the authority for money and Time Matters for the rest.
Do trust balances in Time Matters have a place in Filevine?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Time Matters before the plan is fixed. If Filevine turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Time Matters have a place in Filevine?
Most of it does on paper. Trust ledgers and intake records 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 Time Matters data is loaded into Filevine?
Time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers and intake records 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 Time Matters and into Filevine
Other destinations from Time Matters
Other systems that move 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.
Time Matters and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Time Matters 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.