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

Data migration route

TimeSolv to Neos migration

TimeSolv is a cloud accounting and billing system, and Neos is a cloud case management system for personal injury work. Only part of what TimeSolv holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from TimeSolv to Neos

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

Records in TimeSolv and their place in Neos
RecordIn TimeSolvIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients. They carry billing settings more than case detail.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClients and their contacts; leads are tracked in the CRM.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldNested folders and tags inside TimeSolv, or a linked Dropbox or NetDocuments account.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes on clients and matters.Has a placeCarried across
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCase calendar entries.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldProject management with phases, tasks, estimates and budgets.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldThe core record, entered on the web, on mobile or offline through the TimeSync app.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 balancesHeldHas 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 balances can be applied to approved invoices.To be confirmedConfirmed in the analysis
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 automationHeld in partDocuments can be generated from client and matter data.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldCRM tracks prospects through intake statuses the firm defines.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 TimeSolv.
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.

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. TimeSolv knows clients, jobs, time and invoices. Neos knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Neos are loaded and checked there. The rest is exported from TimeSolv as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If TimeSolv is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

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

Where the data is now

When the destination is a full practice management system, leaving TimeSolv is only part of the job. TimeSolv knows who the client is, what was billed and what is owed. It does not know the court, the other side or the next deadline. Its billing records move across, and the rest of each matter has to be gathered from wherever the firm has been keeping it.

  1. A matter is a billing file

    A TimeSolv matter holds rates, billing arrangements, budgets and balances. The parties, key dates and file notes that a practice management system expects are often in Outlook, a spreadsheet or the paper file. Part of the analysis is asking where those live, and whether they are loaded with the billing data or entered as matters are next worked on.

  2. Trust here, ledger elsewhere

    Client trust balances are kept in TimeSolv, while the bank accounts and general ledger are in QuickBooks, Xero or AccountEdge. The trust listing from TimeSolv and the trust bank balance from the accounting package are agreed with each other before cutover. Only then are opening balances entered in the new system.

  3. Phases, tasks and budgets

    Matter plans split a job into phases and tasks with estimated hours and fixed fees, and time is recorded against task codes. Many destinations bill by matter with no phase beneath it. Where budgets matter to clients, the firm decides whether phases become sub-matters, activity codes or a report run from the old data.

  4. Documents in three places

    Files may be in TimeSolv’s own folders, in a linked Dropbox account or in NetDocuments workspaces. A single firm can have all three if it changed approach over the years. Each store is listed with its volume, and documents already in NetDocuments or Dropbox can often stay where they are.

  5. Many years of time entries

    The product dates from 1999, so a long-standing firm can hold a very long run of billed time in it. Loading all of it into a new system is seldom worth the effort. A common split is open matters with full detail, closed matters as a summary, and the complete history kept in the read-only copy.

More about moving off TimeSolv

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 TimeSolv and checking each trial against TimeSolv.

  1. Analysis

    We read what TimeSolv 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 TimeSolv, 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 TimeSolv: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in TimeSolv 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 TimeSolv as at the cutover date. TimeSolv 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 TimeSolv 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 fromTimeSolv
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 TimeSolv 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

TimeSolv to Neos: what firms ask

We use TimeSolv with QuickBooks. Which one is the source for debtor balances?

TimeSolv, because that is where invoices are raised and payments applied by matter. QuickBooks holds the same totals at firm level once synced. The two are compared in the analysis. A difference usually points to a payment entered on one side only, and it is fixed before the trial load.

Will our unbilled time come across?

Unbilled time and expenses are the records most worth moving, since they are money not yet invoiced. They are loaded against the right matter and timekeeper with their original dates and narratives. Running a final billing cycle in TimeSolv first leaves less work in progress to carry.

We are on the Pro edition, not Legal. Is the move any different?

The records are the same kind: clients, the jobs under them, time, expenses and invoices. Extraction and checking are planned the same way. What changes is the destination, since a system built for law firms will expect matter types and trust rules that a consultancy or accounting practice never needed.

Do trust balances in TimeSolv 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 TimeSolv 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.

Does everything in TimeSolv have a place in Neos?

Most of it does on paper. Emails, calendar entries, trust ledgers 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 Neos is kept as a readable archive, and you see which before the move.

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

Time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Emails, calendar entries, 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

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

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