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

Data migration route

ProTempus to Filevine migration

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

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

What moves

What moves from ProTempus to Filevine

Each row is a kind of record ProTempus holds, whether Filevine has a place for it, and what is planned. On this route five kinds of record carry across, five kinds need mapping and four kinds are confirmed in the analysis.

Records in ProTempus and their place in Filevine
RecordIn ProTempusIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; a client can have several, each with its own rate and billing type.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldClients and other parties, with a role on each case and user-defined contact types.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partNot stored in the program: each client links to a network folder, with keyword indexes.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 partEmails are saved as files into the client’s document folder.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldA calendar per timekeeper, with optional Outlook or Google sync.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime can be created from calendar events and phone calls.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHourly, contingency, flat rate and unit billing; invoices can be split between parties.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust accounting, with invoices payable from the client’s trust balance.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldReceivables, payables and general ledger, or an optional QuickBooks interface.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldBoilerplate forms filled from the database.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partA client’s completed PDF intake form can be imported into the case file.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 ProTempus.
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 ProTempus 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 ProTempus, and kept as the record of what was billed and held.

ProTempus 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

ProTempus keeps its database on the firm’s own network and never took the documents in, so both are close at hand. The detail to watch is how tightly billing is tied to everything else. Calendar entries become charges, cases under one client bill on different terms, and one invoice can be divided among several payers. Those arrangements need to survive the move.

  1. Documents were never imported

    The program does not hold documents. Each client is linked to a folder on the firm’s network, with subfolders for cases, and invoices are saved there as PDFs. The files are already ordinary files. What has to be carried is the link between each client or case and its folder, and any keyword index built on top.

  2. The calendar bills

    A calendar event or logged phone call can be turned into a billable item, and it then shows green. Time entries and calendar entries are therefore two views of the same work. Both are extracted, and the billed flag is checked so that an appointment already charged is not loaded as unbilled time.

  3. Cases under a client

    Each client can have several cases, and each case has its own rate and its own billing type: hourly, contingency, flat rate or unit. By default each case gets its own invoice. A destination that sets billing terms at client level needs those terms moved down to the matter, one case at a time.

  4. Invoices split between payers

    A case’s bill can be divided among any number of parties, each paying a share. The invoice history then shows several debtors for one piece of work. Open balances are loaded against the party who owes them, and the split percentages are recorded on the matter so future bills follow the same rule.

  5. Books inside or QuickBooks

    The firm either uses the embedded payables and general ledger or connects to QuickBooks, where each client’s trust money is a sub-account. Where QuickBooks is used, the program can audit its trust balances against those sub-accounts. That audit is run and cleared before extraction, so both sets of figures start out equal.

More about moving off ProTempus

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 ProTempus 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 ProTempus, 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 ProTempus: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in ProTempus 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. ProTempus 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 ProTempus 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 fromProTempus
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 ProTempus 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

ProTempus to Filevine: what firms ask

Our documents are in folders on the server. Do they move?

They can stay or move. ProTempus only points at those folders, so nothing has to be extracted from the program itself. If the new system stores documents, each client folder is loaded against the matching client and matter. The folder names are checked against the client list first, because renamed folders are the usual cause of orphans.

We enter every caller for conflict checks. Do they all come?

They should. A contact list that includes people who only ever phoned is what makes a conflict search worth running. They are loaded as contacts with no matter attached. The clean-up step looks for the same caller entered more than once, though not every duplicate can be found and some may carry across.

Can trust and operating balances be moved together?

Yes, and they are checked together. Each client’s trust balance is loaded as an opening balance and the total is matched to the bank. Unpaid invoices are loaded as debtors. The trust and financial cutover is rehearsed on a full trial load before the real one, because it cannot be run twice.

Do trust balances in ProTempus 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 ProTempus have a place in Filevine?

Most of it does on paper. Notes, tasks, the firm’s accounts and custom fields 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 ProTempus data is loaded into Filevine?

Time entries, billing records, trust ledgers, templates and intake records are carried with mapping, so each mapping is agreed with you first. Notes, tasks, the firm’s accounts and custom fields are confirmed in the analysis. 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

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

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