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

Data migration route

TimeSolv data to Microsoft SQL Server

TimeSolv is a cloud 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 TimeSolv holds and keeps it readable and open to queries.

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

What moves

What moves from TimeSolv to Microsoft SQL Server

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

Records in TimeSolv and their place in Microsoft SQL Server
RecordIn TimeSolvIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldClients and their contacts; leads are tracked in the CRM.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldNested folders and tags inside TimeSolv, or a linked Dropbox or NetDocuments account.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes on clients and matters.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeRows of appointments and key dates; nothing displays them as a calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldProject management with phases, tasks, estimates and budgets.Has a placeRows with assignee, due date and status.Exported in full
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 placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldHas a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust balances can be applied to approved invoices.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 itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partDocuments can be generated from client and matter data.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldCRM tracks prospects through intake statuses the firm defines.Has a placeEnquiry rows, where the source recorded them.Exported in full

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

TimeSolv is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What TimeSolv will release depends on its export tools, and that is confirmed in the analysis.

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

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 TimeSolv holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything TimeSolv 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 TimeSolv: record counts, totals where TimeSolv 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 TimeSolv, the export is run a final time and checked again. There is nothing to go live. TimeSolv 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 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 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 TimeSolv 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

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

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

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 TimeSolv as at the export date.

Does everything in TimeSolv have a place in Microsoft SQL Server?

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

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

Documents and templates are exported with mapping, so each mapping is agreed with you first. Emails, calendar entries and custom fields 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

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

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