Data migration route
Orion to Box migration
Orion is a practice management system, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
OrionPractice management- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Custom fields: Carried with mapping
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
BoxCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 3 mapped
- 3 to confirm
- 7 archived
What moves
What moves from Orion to Box
Each row is a kind of record Orion holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, seven kinds have no place in Box and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters, with case types the firm defines. | No placeA matter is a folder, optionally with metadata; there is no matter record. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldContact management with firm-defined contact types. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldOwn document management with imaging; also integrates with NetDocuments and Worldox. | Has a placeFiles and folders, named and dated as they are loaded. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails are linked to a client or matter from Outlook. | Has a place in partAs .msg or .eml files in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldJournals record notes and other activity on a case. | Has a place in partAs documents in the matter folder, not as a notes record. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldDocket and calendar. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBilling and accounts receivable. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, accounts payable and AP imaging. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partFirm-defined case types and contact types. | Has a place in partMetadata templates can hold fields such as matter number and client. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as ordinary files; no document automation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- Box has a place for this kind of record. It is loaded there and checked against Orion.
- Carried with mapping
- Box 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
- Box 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 Box 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 Box 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. Box 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
Leaving Orion
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Box
Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.
Decide who owns the top level
Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.
Restricted matters go near the top
Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.
Names Box will not accept
Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.
Matter details become metadata
A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.
File size follows the owner’s plan
The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Orion holds and how it is organised, then agree with you where each kind of record will sit in Box. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Box 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Orion holds
What is in it, how its records link, and where each piece would sit in Box. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
Box 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.
Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.
What is agreed and set up
- Top-level folder structure and who owns each folder
- Groups for teams, mapped to collaborator roles
- Metadata template for matter number, client and status
- Shared link defaults and rules for external collaborators
- Box Drive installed and signed in on each PC
- Version limits and retention agreed with the firm’s records policy
Questions
Orion to Box: 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 Box?
No. Box 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 Box has no place for?
On this route that is matters, contacts, calendar entries, 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 Box?
Emails, notes 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.
Other routes
Other routes from Orion and into Box
Other destinations from Orion
Other systems that move into Box
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Orion and Box are the names and marks of their owners, used here only to identify the two systems.
Moving from Orion to Box?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.