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

Data migration route

Sage Timeslips data to Microsoft SQL Server

Sage Timeslips is a desktop accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Sage Timeslips holds and keeps it readable and open to queries.

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

What moves

What moves from Sage Timeslips to Microsoft SQL Server

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

Records in Sage Timeslips and their place in Microsoft SQL Server
RecordIn Sage TimeslipsIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeld in partClients and their contacts.Has a placePeople and companies, with their roles on each matter.Exported in full
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entries, called slips.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBills the firm designs itself, payments and receivable balances.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partClient funds accounts track money held for clients.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Custom fieldsFields and record types the firm added itselfHeldHas a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partBill layouts designed in the product.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Sage Timeslips.
Exported with mapping
Microsoft SQL Server 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

Not a new system. A complete copy the firm can query.

Writing Sage Timeslips out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Sage Timeslips as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Sage Timeslips stays untouched until the copy in Microsoft SQL Server has been checked.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Sage Timeslips holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Sage Timeslips holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Sage Timeslips: record counts, totals where Sage Timeslips holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Sage Timeslips, the export is run a final time and checked again. There is nothing to go live. Sage Timeslips is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Sage Timeslips to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from Sage Timeslips?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Sage Timeslips as at the export date.

Does everything in Sage Timeslips have a place in Microsoft SQL Server?

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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Sage Timeslips is written out to Microsoft SQL Server?

Custom fields and templates are exported with mapping, so each mapping is agreed with you first. Notes are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Sage Timeslips to Microsoft SQL Server?

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

We reply within one business day.