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

Data migration route

ProTempus to Neos migration

ProTempus is a server-based practice management system, and Neos is a cloud case management system for personal injury work. 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. Calendar: Carried across
  5. Intake: Carried across
  6. Emails: Carried with mapping
  7. Time and expenses: Carried with mapping
  8. Billing: Carried with mapping
  9. Templates: Carried with mapping
  10. Notes: Confirmed in the analysis
  11. Tasks: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 5 carried
  • 4 mapped
  • 4 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ProTempus to Neos

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

Records in ProTempus and their place in Neos
RecordIn ProTempusIn NeosWhat 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 placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClients and other parties, with a role on each case and user-defined contact types.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.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 placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails are saved as files into the client’s document folder.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldA calendar per timekeeper, with optional Outlook or Google sync.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed 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 partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHourly, contingency, flat rate and unit billing; invoices can be split between parties.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust accounting, with invoices payable from the client’s trust balance.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldReceivables, payables and general ledger, or an optional QuickBooks interface.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldBoilerplate forms filled from the database.Has a place in partTemplates are rebuilt for Neos document generation.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 placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against ProTempus.
Carried with mapping
Neos 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.
Kept as a readable archive
Neos has no place for it. It is exported in a format that opens without ProTempus and handed to the firm as a read-only archive.

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 Neos. 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 Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos 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. Neos 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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in ProTempus and checking each trial against ProTempus.

  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 Neos. 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 Neos as a trial and checked against ProTempus: record counts, financial 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 Neos 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 ProTempus as at the cutover date. 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

ProTempus to Neos: 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 Neos?

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 ProTempus before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from ProTempus in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before ProTempus data is loaded into Neos?

Emails, time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers 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 Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from ProTempus to Neos?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.