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

Data migration route

MyCase data to Microsoft SQL Server

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

FromMyCaseCloud
  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. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Firm accounts: Exported in full
  10. Intake: Exported in full
  11. Documents: Exported with mapping
  12. Emails: Exported with mapping
  13. Custom fields: Exported with mapping
  14. Templates: Exported with mapping
ToMicrosoft SQL ServerServer
  • 10 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from MyCase to Microsoft SQL Server

Each row is a kind of record MyCase holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route ten kinds of record carry across and four kinds need mapping.

Records in MyCase and their place in Microsoft SQL Server
RecordIn MyCaseIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases. Each has a unique name, an optional case number, a practice area and an open or closed state.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldContacts (people) and companies are separate record types, linked to cases.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldStored against cases in folders, with version tracking and unlimited storage.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 storeHeld in partOnly emails linked through the Outlook or Gmail add-ins or a forwarding address.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 notesHeldHas a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldCan sync with Google Calendar and Outlook.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow automation.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldHas 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 balancesHeldHas a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partMyCase Accounting is an add-on; a QuickBooks sync is the alternative.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom fields on cases and on contacts.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldWord-based document templates and automation.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads in a Kanban view, with intake forms that can be embedded on a website.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 MyCase.
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.

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

MyCase 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 MyCase will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

A firm leaving MyCase is moving a set of cases with everything tied to them, and the first job is working out which of those ties the next system can hold. Documents, time, invoices and trust balances have obvious homes. Portal messages, text conversations and the lead pipeline often do not, so each is given a destination or a reason to stay behind before any data is extracted.

  1. Cases, contacts and companies

    MyCase says case where most systems say matter, and it keeps people and companies as two separate record types. A destination that has one contact card for both, or that insists on a client record above each matter, needs a rule for which MyCase contact becomes the client when a case has several linked to it.

  2. Case numbers are optional

    The case number is a free-text field that a firm can leave empty or fill with a court file number. If the new system wants a unique matter number on every record, the analysis finds the cases with no number or a shared one, and the firm agrees how those are numbered.

  3. Only linked emails are there

    Emails reach a case through the Gmail or Outlook add-ins, or by forwarding to a personal MyCase address. Anything nobody linked is still in a mailbox, and emails the software could not match wait in an Unresolved Emails queue. That queue is worth clearing before extraction, because unmatched emails have no case to travel with.

  4. Books may sit elsewhere

    Invoices, payments and trust ledgers are inside MyCase. The general ledger is either the MyCase Accounting add-on or QuickBooks fed by a sync. Where QuickBooks is in use, debtor and trust totals are taken from both and compared before cutover, so the opening figures in the new system are ones the bookkeeper recognises.

  5. Messages and texts

    Client portal messages and text conversations are saved against the case. Few systems have a matching record type. They are usually carried as a dated note or a single document on each matter, and the firm sees an example of how that reads before deciding whether it is enough.

More about moving off MyCase

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

MyCase to Microsoft SQL Server: what firms ask

Can we keep our existing matter numbers when we move to MyCase?

Yes. The case number field accepts letters, digits and special characters, so numbers can go in exactly as they are. MyCase does not require the number to follow a pattern. What it does require is a unique case name, so the naming rule usually takes more discussion than the numbering.

We are leaving MyCase. Do our client portal messages come with us?

They can be kept, but rarely as live messages. Most systems have no record that matches a MyCase portal thread, so the messages are carried as dated notes or one document per matter. Whether the destination has anything closer is confirmed in the analysis, and the firm sees a sample first.

What happens to closed cases?

They move as closed, with their closed date, documents and billing history where the destination has a place for it. Some firms bring across only matters closed within a set number of years and keep the older ones in the read-only copy of the old system. That choice is made before the trial load.

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

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

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

On paper, yes: each kind of record MyCase holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

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

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

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