Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Lawmatics to Filevine migration

Lawmatics is a cloud CRM and intake system, and Filevine is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Filevine.

FromLawmaticsCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Intake: Carried with mapping
ToFilevineCloud
  • 7 carried
  • 6 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Lawmatics to Filevine

Each row is a kind of record Lawmatics holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across and six kinds need mapping.

Records in Lawmatics and their place in Filevine
RecordIn LawmaticsIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA matter is a lead, a client or a lost enquiry, with a status of PNC, Hired or Lost.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldContacts and companies; other parties link to a matter as relationships.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partA Files tab with folders on each matter. Files download one matter at a time.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partMail sync logs emails with known contacts on the matter timeline.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldAppointments with event types, synced with Google, Outlook or iCloud calendars.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks with custom statuses and tags.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime entries and expenses, in the Time & Billing module.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments, in the Time & Billing module.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partA trust account with a running balance per matter, in the Time & Billing module.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldCustom fields on matters, contacts and companies.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, email templates, custom forms and automations.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldPipelines, custom forms, booking links, marketing sources and campaigns.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 Lawmatics.
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.

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

Intake history moves. The pipeline is rebuilt.

Intake data is the front end of a case. A lead in Lawmatics carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Filevine has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.

Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Filevine or in the tool that feeds it.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lawmatics 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 Lawmatics is kept running until the checks on Filevine are finished.

Where the data is now

Lawmatics will export matters, contacts and companies as CSV files with every field, custom fields included. Files are different: they cannot be exported for all matters at once. So a move off it runs in two streams, a quick one for the structured records and a slower one that collects each matter’s files, notes and timeline.

  1. Three statuses, one record type

    Leads, clients and lost enquiries are all matters, told apart by a status of PNC, Hired or Lost and any sub-statuses the firm added. A practice system usually wants only the hired ones as matters. The others go to its intake side if it has one, or are kept as contacts with a note of the enquiry.

  2. Files come out matter by matter

    The bulk export covers records and fields. Files saved on matters, the vendor’s help centre says plainly, cannot be exported for all matters at once in the app, only downloaded matter by matter. The API also exposes files and folders, which is the other route for any real volume. Either way the result is checked against a count for each matter.

  3. Relationships are separate contacts

    A spouse, a co-defendant or a referring lawyer is linked to a matter through a relationship type the firm defined, and each is a full contact in the CRM. Those links are exported with the matter and mapped to the destination’s party roles. Where a role has no equivalent, the firm chooses the nearest one.

  4. Often already synced elsewhere

    Plenty of firms have Lawmatics pushing hired matters into Clio Manage or another practice system. That sync runs mostly one way, and notes, files or fields added in Lawmatics afterwards cross only when someone presses Sync again. Before a move the two systems are compared, so the later additions are not lost.

  5. Automations and forms

    Intake forms, email campaigns and automations do the daily work in this product, and none of them export as something another system can run. Each live automation is documented with its trigger and steps. Forms embedded in the firm’s website are replaced at cutover so enquiries stop arriving in the old account.

More about moving off Lawmatics

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Lawmatics 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Lawmatics, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against Lawmatics: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Lawmatics are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Lawmatics 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 Lawmatics 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

Step 1 of 5: Start with the route

Moving fromLawmatics
Moving toFilevine

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Lawmatics 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.

  3. 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

Lawmatics to Filevine: what firms ask

Can we move from Lawmatics into a full practice management system?

Yes. Hired matters and their contacts map naturally onto clients and matters, and the custom fields come out in the same export. What needs thought is the enquiries that never became clients. A destination with an intake module can take them as leads. Otherwise they are kept as contacts, or left in the export file.

Do the files on each matter come with it?

They do, but not through the bulk export, which covers records only. Files are downloaded per matter or pulled through the API with their folder names. Signed engagement documents and completed intake forms are saved to the Files tab automatically, so those are included. The trial load compares file counts matter by matter.

What happens to our trust balances in Lawmatics?

The trust account table exports to CSV as filtered on screen, showing deposits, payments and a running balance. Balances per matter are rebuilt in the destination from that table and agreed to the bank statement before cutover. The trust cutover is rehearsed on a full trial load first, because it cannot simply be run again.

Do trust balances in Lawmatics have a place in Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Lawmatics have a place in Filevine?

On paper, yes: each kind of record Lawmatics holds has a place in Filevine. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Lawmatics data is loaded into Filevine?

Time entries, billing records, trust ledgers, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.

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.

How we do itDiscovery to rollout, step by step

Lawmatics and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Lawmatics 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.