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

Data migration route

Orion to SharePoint migration

Orion is a practice management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromOrionPractice management
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Tasks: Confirmed in the analysis
  9. Templates: Confirmed in the analysis
  10. Intake: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Firm accounts: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 6 mapped
  • 3 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Orion to SharePoint

Each row is a kind of record Orion holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, six kinds need mapping, four kinds have no place in SharePoint and are archived and three kinds are confirmed in the analysis.

Records in Orion and their place in SharePoint
RecordIn OrionIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with case types the firm defines.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldContact management with firm-defined contact types.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldOwn document management with imaging; also integrates with NetDocuments and Worldox.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are linked to a client or matter from Outlook.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldJournals record notes and other activity on a case.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldDocket and calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a place in partPossible as a list; no legal workflow built in.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling and accounts receivable.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldNo placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable and AP imaging.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partFirm-defined case types and contact types.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against Orion.
Carried with mapping
SharePoint 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
SharePoint has no place for it. It is exported in a format that opens without Orion 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Orion into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Orion.

How Orion is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Orion 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. SharePoint 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

Orion began as an accounting system and the accounts are still its foundation. A firm leaving it is moving its general ledger, payables and trust along with its matters, and all of them have to agree on the other side. The other question is documents, which may be in Orion’s own document management or in a separate product connected to it.

  1. The books come too

    Billing, receivables, payables, the general ledger and trust accounting are all inside Orion. If the destination has no general ledger of its own, the firm needs an accounting package beside it and the ledger is split between two systems. That decision is made first, because it sets what the financial trial load is checked against.

  2. Which document store

    Some firms use Orion Document Management. Others connect Orion to NetDocuments or Worldox and keep their files there. In the second case the documents are not part of this move unless the firm wants them to be. Where the files are, and whether they are staying, is the first thing asked about documents.

  3. Journals hold the history

    A case journal records the activity on a matter: emails, documents, files from other applications and notes. It reads as one running history. A destination will separate these into notes, emails and documents, and the order between them can be lost. Dates and authors are preserved on every item so the sequence can be rebuilt.

  4. Scanned supplier invoices

    Accounts payable includes imaging, so a payable may have a scan of the supplier’s invoice attached. Where that expense was charged to a client, the image is the evidence for the disbursement. The images are extracted with their transactions and filed against the matter or the payable in the new system.

  5. On premise or Orion Cloud

    Orion is offered both installed on the firm’s servers and from the vendor’s cloud. The records are the same. What differs is where the database is and who can give access to it. That is settled at the start, and the same collection method is then used for the trial load and for cutover.

More about moving off Orion

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Orion holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against Orion: 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 Orion, a final pass over a weekend picks up what changed since the trial. Orion 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 Orion 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 fromOrion
Moving toSharePoint

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 Orion holds

    What is in it, how its records link, and where each piece would sit in SharePoint. 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

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Orion to SharePoint: what firms ask

Can we move our trust accounts mid-month?

It is possible but a month end is cleaner. Trust is reconciled in Orion to the cutover date, each matter’s balance is loaded as an opening balance, and the total is matched to the bank statement. The whole sequence is rehearsed on a full trial load first, since the financial cutover cannot be re-run.

Do our custom case types carry across?

The case types themselves are a list, and the list is rebuilt in the new system. The fields that belong to each type need more care. Each one in use is mapped to a field or a custom field at the destination, and types that were set up years ago and never used are left out with the firm’s agreement.

Our documents are in Worldox, linked to Orion. What changes?

The documents can remain in Worldox. What changes is the link, which runs on client and matter numbers. If those numbers are kept in the new system, the link can usually be re-established. If the firm is renumbering, a cross-reference of old and new numbers is produced so the document store can be updated.

Do trust balances in Orion have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Orion are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers and the firm’s accounts. They are exported from Orion 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 Orion data is loaded into SharePoint?

Matters, contacts, emails, notes, calendar entries and custom fields are carried with mapping, so each mapping is agreed with you first. Tasks, templates and intake records 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

Orion and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Orion to SharePoint?

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

We reply within one business day.