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

Data migration route

Open Case Management (OCM) data to Microsoft SQL Server

Open Case Management (OCM) is a server-based case management system for legal aid work, 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 Open Case Management (OCM) holds and keeps it readable and open to queries.

FromOpen Case Management (OCM)Server
  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. Intake: Exported in full
  8. Documents: Exported with mapping
  9. Custom fields: Exported with mapping
  10. Templates: Exported with mapping
  11. Emails: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 7 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Open Case Management (OCM) to Microsoft SQL Server

Each row is a kind of record Open Case Management (OCM) holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and one kind is confirmed in the analysis.

Records in Open Case Management (OCM) and their place in Microsoft SQL Server
RecordIn Open Case Management (OCM)In Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, each started from an intake.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldClients, adverse parties and contacts on every case, with duplicate merging.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldUploaded files indexed for search, including PDFs and WordPerfect documents.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 notesHeldHas a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldShared calendars with iCal feeds.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTicklers.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips on every case.Has a placeTime and expense rows with rates and billed status.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom fields, HTML fields and editable menus.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldForm letters and generated documents using configurable template tags.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with financial and citizenship eligibility, conflict and duplicate checks.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 Open Case Management (OCM).
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 Open Case Management (OCM) 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 Open Case Management (OCM) 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 Open Case Management (OCM) stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Where OCM is self-hosted, the database and the uploaded files are on a server the program or its host controls. That makes collection simple and makes the mapping the real work. The records were designed for legal aid reporting: intakes that may never become cases, eligibility answers, timeslips and the codes that funders count. Each needs a place or a decision.

  1. Intakes that never became cases

    An intake is started, screened for financial and citizenship eligibility, checked for conflicts and duplicates, then reviewed and assigned. Many stop before a case is opened. Those records still matter, because a person turned away last year is a conflict check hit this year. They are loaded as contacts with a note, or as closed enquiries.

  2. WordPerfect files in the store

    Uploaded documents are indexed for search, and the project documents support for WordPerfect files as well as PDFs. Programs that have run for decades often have both. Files move in their original format. Whether the new system can preview or search a WordPerfect document is tested in the trial load, not assumed.

  3. Menus the program edited

    Menus, custom fields and HTML fields can all be changed by the program, so the values on a case come from lists that are local to that site. Every list is exported with its codes and labels. Retired values that still appear on old cases are kept, since deleting them would blank the field on those records.

  4. MegaReport queries

    Staff build their own ad hoc reports with a tool called MegaReport, alongside the built-in reports and LSC case service reporting. Saved queries are not data and do not migrate. The ones still used are listed, and each is either rebuilt in the new system or replaced by an export the program can run itself.

  5. Peer transfers between programs

    Cases can be transferred to a peer program running the same software. A transferred case has a history that began somewhere else. These are identified in the analysis so that the originating program, the transfer date and any documents that arrived with the case are preserved on the record.

More about moving off Open Case Management (OCM)

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

Open Case Management (OCM) to Microsoft SQL Server: what firms ask

We run OCM on our own server. Does that make moving easier?

It makes getting the data out easier, because the database and the uploaded files are under the program’s control and can be copied in full. It does not shorten the mapping or the checking. A complete copy is taken for the trial load, and a second one at cutover after changes are frozen.

We are told OCM has been renamed. Does that force a move?

No one has to move because of a name. The open-source code is still published and receives security and bug fixes, and the commercial version continues as Ciprocity. Whether and when to move is the program’s own decision. If a move is planned, the installed version is identified first.

What happens to closed cases and old intakes?

Both are normally brought across. Legal aid programs rely on old records for conflict checks and funder audits, so leaving them behind saves little. If volume is a concern, the names and case numbers are loaded for every record and the full detail only from a chosen year onwards, with the remainder kept read only.

Does the copy in Microsoft SQL Server hold documents from Open Case Management (OCM)?

In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Open Case Management (OCM).

Does everything in Open Case Management (OCM) have a place in Microsoft SQL Server?

Most of it does on paper. Emails 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 Open Case Management (OCM) is written out to Microsoft SQL Server?

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

Open Case Management (OCM) and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Open Case Management (OCM) 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.