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

Data migration route

Legal Files data to Microsoft SQL Server

Legal Files are a server-based case management 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 Legal Files hold and keeps it readable and open to queries.

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

What moves

What moves from Legal Files to Microsoft SQL Server

Each row is a kind of record Legal Files hold, whether Microsoft SQL Server has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and three kinds are confirmed in the analysis.

Records in Legal Files and their place in Microsoft SQL Server
RecordIn Legal FilesIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAny type of case or matter, as configured by the organisation.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldContact management with checks for duplicate entries.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocument management with text searching.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 storeHeldTwo-way integration with Outlook and Gmail saves emails and attachments.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes, mail logs and phone logs.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldCalendaring with deadline tracking.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows, alerts and follow-ups.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeTime and expense rows with rates and billed status.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partThe vendor lists eBilling among its functions.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTransactions and balances for look-up; it is not a trust accounting system.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger journals and balances, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustomers add and change fields and screens without programming.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLegal aid intake is among the uses the vendor describes.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 Legal Files.
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 Legal Files 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 Legal Files 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 Legal Files stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Each office configured its own file types, fields and workflows, so one Legal Files system does not look like the next. The move starts with an inventory of that configuration. Then come the files, the people on them, documents and saved emails. Where the office is part of a government body or a company, retention rules and access restrictions on certain files have to survive the move as well.

  1. Configuration is the data model

    File types, screens and fields were set up by the office’s own administrator, often over many years. The field list has to be taken from that system, not assumed. Every custom field is reported with how many files use it, and the office picks the ones that deserve a place in the new system.

  2. Not built around billing

    Many of its users are in-house and government teams, which do not bill clients or hold trust money. If the destination is a law firm practice system, billing fields will be empty on every migrated matter. Where the office does record time or outside counsel spend, that is found in the analysis and mapped separately.

  3. Mail and phone logs

    Besides documents and emails, a file keeps logs of mail and of phone calls. Offices that answer to the public rely on these as the record of who was told what. They come across as dated notes on the matter with the log type kept, so they can still be filtered.

  4. Restricted files

    Investigations and other sensitive files are kept under controlled access. Those restrictions are extracted as a list of files and the users allowed to see them. The destination’s permissions are set from that list before the trial load is opened to staff, so restricted files are locked down before anyone else looks.

  5. On your servers or hosted

    The route to a copy of the data depends on where Legal Files runs. An on-premises site works through its own IT team. A hosted site works through the vendor. Government sites often need a security review before data leaves the building, and that review goes in the timetable.

More about moving off Legal Files

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

Legal Files to Microsoft SQL Server: what firms ask

Our system has been heavily customised. Does everything have to be rebuilt?

No. Custom fields that are still filled in are recreated. Ones that were abandoned years ago are reported and usually left behind. Workflows and document templates do not transfer between products, so the ones in regular use are rebuilt in the new system and the rest are retired.

Can saved emails stay attached to the right file?

Emails saved into Legal Files through its Outlook or Gmail integration are stored against the file, with attachments. They are loaded to the same matter in the destination with their sent date and sender kept. Counts are run per file, because saved emails are easy to lose in a move without anyone noticing.

What about records we are required to retain?

Retention obligations travel with the records, not the software. Files due to be kept are either loaded as closed matters or held in a read-only copy of Legal Files for the retention period. The choice is written down with the office’s records officer, along with who can reach the copy.

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

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 Legal Files before the plan is fixed.

Does everything in Legal Files have a place in Microsoft SQL Server?

Most of it does on paper. Time entries, trust ledgers and the firm’s accounts 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 Legal Files are written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Time entries, trust ledgers and the firm’s accounts 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

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

Moving from Legal Files 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.