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

Data migration route

Sage Timeslips to Gladiate migration

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

FromSage TimeslipsDesktop
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Templates: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Time and expenses: Confirmed in the analysis
  6. Billing: Confirmed in the analysis
  7. Trust money: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
ToGladiateCloud
  • 2 carried
  • 1 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Sage Timeslips to Gladiate

Each row is a kind of record Sage Timeslips holds, whether Gladiate has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and five kinds are confirmed in the analysis.

Records in Sage Timeslips and their place in Gladiate
RecordIn Sage TimeslipsIn GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partBills by client; many firms enter each matter as its own client.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersHeld in partClients and their contacts.Has a placeClients, leads and referral sources.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entries, called slips.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldBills the firm designs itself, payments and receivable balances.To be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient funds accounts track money held for clients.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partBill layouts designed in the product.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping

What the plans mean

Carried across
Gladiate has a place for this kind of record. It is loaded there and checked against Sage Timeslips.
Carried with mapping
Gladiate 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. Sage Timeslips knows clients, jobs, time and invoices. Gladiate 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 Gladiate are loaded and checked there. The rest is exported from Sage Timeslips as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Sage Timeslips 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.

Sage Timeslips 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. Gladiate 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

Timeslips does one job, so a move off it is about time, bills and balances, with matters and contacts built from what the billing records imply. The main decision is how the firm used the client list. Some entered one client per matter, others one per person. That convention is read from the data before any mapping is done.

  1. A client may be a matter

    The program bills clients, and firms that needed matters adapted the client list to carry them. A common pattern is one Timeslips client per matter, with the two nickname fields holding the client name and the matter. The move turns that into clients with matters beneath, which means deciding which entries are the same person.

  2. Slips are the history

    Each piece of time and each expense is a slip with a date, timekeeper, activity, rate and billing status. Unbilled slips become unbilled time and disbursements in the destination. Billed slips are history, loaded where the new system accepts billed entries and otherwise left in a read-only copy with the invoices.

  3. Client funds and trust

    Money held for a client is tracked in client funds accounts inside Timeslips. A firm that holds trust money may also keep a formal trust ledger and bank reconciliation in an accounting program. Both are looked at, and the balance loaded as trust is the one that agrees to the bank.

  4. Firebird behind the program

    Timeslips Premium stores its data in a Firebird database, either on one PC or on a database server for network installs. On a network the database components sit on the server and the program in a shared folder. A backup made from inside Timeslips gives a copy to work from without disturbing the live database.

  5. The books are in another product

    Receivables are kept in Timeslips, but the firm’s general ledger sits in a separate accounting package. The receivable balance in Timeslips and the debtors figure in that package should agree before cutover. Where they have drifted apart, the firm decides which is right before either is loaded.

More about moving off Sage Timeslips

Where it is going

Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.

  1. Injury fields come first

    Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.

  2. Templates and task plans

    The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.

  3. A folder structure per case

    Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.

  4. What it may not hold

    Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.

More about moving into Gladiate

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Sage Timeslips holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Gladiate and checked against Sage Timeslips: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    After a short freeze on changes in Sage Timeslips, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Sage Timeslips 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 Sage Timeslips 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 fromSage Timeslips
Moving toGladiate

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 Sage Timeslips holds

    What is in it, how its records link, and where each piece would sit in Gladiate. 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 Gladiate

Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.

Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.

Set-up decisions in Gladiate

  • Set up and test the firm’s document templates
  • Write task plans for each stage of a case
  • Agree one folder structure for case documents
  • Enter litigation deadlines for the firm’s jurisdictions
  • Prepare client questionnaires, surveys and scheduled case updates
  • Connect Outlook or Google calendars for two-way sync

Questions

Sage Timeslips to Gladiate: what firms ask

Can we split our client list into clients and matters?

Yes, and it is usually the main clean-up task. The analysis groups Timeslips clients that look like the same person or company and proposes a client with matters beneath. Someone at the firm then reviews the list, because only a person who knows the files can say whether two similar names are one client.

Do our bill layouts carry over?

No. Layouts designed in Timeslips belong to it. The firm chooses the formats it still sends, and each is rebuilt as an invoice template in the new system. Clients who receive LEDES files are tested separately with a real invoice before the first live bill run.

What happens to our custom fields?

Custom fields are listed with how often they are filled, and the ones that matter are mapped to fields on the client or matter in the new system. A field that only ever held a matter number or a file reference usually becomes the matter number itself.

Do trust balances in Sage Timeslips have a place in Gladiate?

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 Sage Timeslips before the plan is fixed. If Gladiate 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 Sage Timeslips have a place in Gladiate?

Most of it does on paper. Notes, time entries, billing records, 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 Gladiate is kept as a readable archive, and you see which before the move.

What has to be decided before Sage Timeslips data is loaded into Gladiate?

Templates are carried with mapping, so each mapping is agreed with you first. Notes, time entries, billing records, trust ledgers and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Sage Timeslips and Gladiate are the names and marks of their owners, used here only to identify the two systems.

Moving from Sage Timeslips to Gladiate?

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

We reply within one business day.