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

Data migration route

Orion data to Microsoft SQL Server

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

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

What moves

What moves from Orion to Microsoft SQL Server

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

Records in Orion and their place in Microsoft SQL Server
RecordIn OrionIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with case types the firm defines.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldContact management with firm-defined contact types.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldOwn document management with imaging; also integrates with NetDocuments and Worldox.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 storeHeldEmails are linked to a client or matter from Outlook.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 notesHeldJournals record notes and other activity on a case.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldDocket and calendar.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows with assignee, due date and status.Confirmed in the analysis
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 balancesHeldBilling and accounts receivable.Has 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 payablesHeldGeneral ledger, accounts payable and AP imaging.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partFirm-defined case types and contact types.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedent files can be stored; automation does not run here.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeEnquiry rows, where the source recorded them.Confirmed in the analysis

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

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. 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 Orion stays untouched until the copy in Microsoft SQL Server has been checked.

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

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

Orion to Microsoft SQL Server: 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.

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

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

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

Most of it does on paper. Tasks, templates and intake records 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 Orion is written out to Microsoft SQL Server?

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

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

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