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

Data migration route

Sage Timeslips to SimpleLaw migration

Sage Timeslips is a desktop accounting and billing system, and SimpleLaw is a cloud practice management system. The financial records lead: balances and open items move, and the matters in SimpleLaw are built around them.

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

What moves

What moves from Sage Timeslips to SimpleLaw

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

Records in Sage Timeslips and their place in SimpleLaw
RecordIn Sage TimeslipsIn SimpleLawWhat 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 placeCarried across
ContactsClients, other parties and referrersHeld in partClients and their contacts.Has a placeAs leads, clients or other contacts in the CRM.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entries, called slips.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeldBills the firm designs itself, payments and receivable balances.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partClient funds accounts track money held for clients.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldHas a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeld in partBill layouts designed in the product.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Sage Timeslips.
Carried with mapping
SimpleLaw 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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Sage Timeslips needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Sage Timeslips. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in SimpleLaw are agreed to the trial balance and aged debtors from Sage Timeslips as at the cutover date, and that load is rehearsed before it is done for real.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

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 Sage Timeslips holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. 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 Sage Timeslips, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Sage Timeslips are frozen for an agreed window, the data is collected a final time and SimpleLaw 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. 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Sage Timeslips to SimpleLaw: 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 SimpleLaw?

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw 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 Sage Timeslips have a place in SimpleLaw?

Most of it does on paper. Notes 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 SimpleLaw 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 SimpleLaw?

Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes 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

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

Moving from Sage Timeslips to SimpleLaw?

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

We reply within one business day.