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

Data migration route

Orion to Sync.com migration

Orion is a practice management system, and Sync.com 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. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Tasks: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
  6. Intake: Confirmed in the analysis
ToSync.comCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Billing: Kept as a readable archive
  6. Trust money: Kept as a readable archive
  7. Firm accounts: Kept as a readable archive
  8. Custom fields: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 2 mapped
  • 3 to confirm
  • 8 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Orion to Sync.com

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

Records in Orion and their place in Sync.com
RecordIn OrionIn Sync.comWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with case types the firm defines.No placeA matter is a folder in Files or Vault.Kept as a readable archive
ContactsClients, other parties and referrersHeldContact management with firm-defined contact types.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldOwn document management with imaging; also integrates with NetDocuments and Worldox.Has a placeFiles and folders within the path limit; some file types are skipped by the apps.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are linked to a client or matter from Outlook.Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldJournals record notes and other activity on a case.Has a place in partOnly as a document written out to the matter’s folder.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldDocket and calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed 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.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as ordinary files.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
Sync.com has a place for this kind of record. It is loaded there and checked against Orion.
Carried with mapping
Sync.com 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
Sync.com 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 Sync.com 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 Sync.com 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. Sync.com 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

A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.

  1. Files or Vault

    Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.

  2. A 248 character path limit

    Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.

  3. What the apps leave out

    The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.

  4. Permissions come from the top folder

    Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.

  5. Shared folders count against storage

    A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.

More about moving into Sync.com

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Sync.com 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 Sync.com. 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 Sync.com 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 toSync.com

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 Sync.com. 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

Sync.com 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.

A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.

What is agreed and set up

  • Administrator account and a user for each staff member
  • Two-factor authentication enforced across the firm
  • Team shared folders with view or edit permission per person
  • Which matters live in Files and which in Vault
  • Rules for client links: passwords, expiry dates, upload rights
  • Desktop app installed, with a filing guide for new matters

Questions

Orion to Sync.com: 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 Sync.com?

No. Sync.com 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 Sync.com has no place for?

On this route that is matters, contacts, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts and custom fields. 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 Sync.com?

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

Moving from Orion to Sync.com?

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

We reply within one business day.