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

Data migration route

Open Case Management (OCM) to NetDocuments migration

Open Case Management (OCM) is a server-based case management system for legal aid work, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromOpen Case Management (OCM)Server
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
  5. Emails: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 3 mapped
  • 2 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Open Case Management (OCM) to NetDocuments

Each row is a kind of record Open Case Management (OCM) holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, five kinds have no place in NetDocuments and are archived and two kinds are confirmed in the analysis.

Records in Open Case Management (OCM) and their place in NetDocuments
RecordIn Open Case Management (OCM)In NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, each started from an intake.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClients, adverse parties and contacts on every case, with duplicate merging.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldUploaded files indexed for search, including PDFs and WordPerfect documents.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNo placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldShared calendars with iCal feeds.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTicklers.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips on every case.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields, HTML fields and editable menus.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldForm letters and generated documents using configurable template tags.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with financial and citizenship eligibility, conflict and duplicate checks.No placeKept as a readable archive

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Open Case Management (OCM).
Carried with mapping
NetDocuments 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.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without Open Case Management (OCM) and handed to the firm as a read-only archive.

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Open Case Management (OCM) is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Open Case Management (OCM) for matters and billing, or into an archive.

Open Case Management (OCM) runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. NetDocuments is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

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

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Open Case Management (OCM) holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into NetDocuments and checked against Open Case Management (OCM): record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Open Case Management (OCM), a final pass over a weekend picks up what changed since the trial. Open Case Management (OCM) is kept read only as the fall-back record.

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 toNetDocuments

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

Setting up NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Open Case Management (OCM) to NetDocuments: 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.

Do documents from Open Case Management (OCM) keep their folders and dates in NetDocuments?

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

What happens to records NetDocuments has no place for?

On this route that is contacts, notes, calendar entries, time entries and intake records. They are exported from Open Case Management (OCM) in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Open Case Management (OCM) data is loaded into NetDocuments?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and tasks are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Moving from Open Case Management (OCM) to NetDocuments?

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

We reply within one business day.