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

Data migration route

Firm Central to NetDocuments migration

Firm Central is a cloud practice management system, 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.

FromFirm CentralCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Tasks: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
  7. Intake: 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. Billing: Kept as a readable archive
  6. Trust money: Kept as a readable archive
  7. Firm accounts: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 1 mapped
  • 5 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Firm Central to NetDocuments

Each row is a kind of record Firm Central holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, seven kinds have no place in NetDocuments and are archived and five kinds are confirmed in the analysis.

Records in Firm Central and their place in NetDocuments
RecordIn Firm CentralIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen and closed matters with practice area, client group, permissions and primary attorney.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, contacts and client groups.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldMatter folders that could be layered freely, plus a My Documents area for each user.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 notesHeldMatter notes.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCalendar events, and Deadline Assistant events for firms that had that add-on.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldMatter tasks.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeld in partThrough the Time & Billing module, which was supplied by eBillity.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partPre-bills, invoices and payments in the Time & Billing module.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partThe Time & Billing module had a Trusts & Retainers tab.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partEditions sold with Accounting had a chart of accounts and accounts payable.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Firm Central.
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 Firm Central 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 Firm Central 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 Firm Central for matters and billing, or into an archive.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Firm Central depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Firm Central is kept running until the checks on NetDocuments are finished.

Where the data is now

Firm Central was discontinued in 2024, so a move from it today starts with whatever the firm saved before the shutdown. Thomson Reuters’ extraction guide had firms download their data as a set of CSV files and zipped document bundles. The job is to find those files, work out what each contains, and rebuild matters from the pieces in a system the firm now uses.

  1. The source is an export

    What survives is a collection of downloads: contact and matter lists, document bundles and calendar files, saved by whoever ran the export in 2024. They may sit on one person’s computer. The analysis begins with an inventory of those files, including their dates, since an export taken weeks before the shutdown misses later work.

  2. One file per kind of record

    Matter lists, matter notes, matter tasks, billing rates, permissions and primary attorneys were each exported as their own CSV, and separately for open and closed matters. Each file is a flat list. The pieces are joined back together on the matter and client they name, and rows that match nothing are listed for the firm.

  3. Documents came out as zips

    Bulk document extraction produced zipped bundles holding each matter’s folders, with files in the format they were uploaded in. Firm Central allowed folders to be layered freely, so structures vary from matter to matter. Each user’s My Documents came out as a separate set and has no matter attached until someone assigns one.

  4. Billing sat with eBillity

    Time entries, invoices, payments and trust records were in the Time & Billing module, which eBillity supplied. Thomson Reuters told firms they could carry on with those eBillity products under a new billing arrangement. A firm that did so has its billing history in eBillity, not in the Firm Central export.

  5. What the export left out

    The guide notes that client portal messages could not be exported, and that links to Westlaw research saved in matter folders do not include the documents themselves. Neither can be recovered from the files. If either mattered to a particular matter, the firm’s email and Westlaw folders are the places to look.

More about moving off Firm Central

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 Firm Central 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 Firm Central: 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 Firm Central, a final pass over a weekend picks up what changed since the trial. Firm Central 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 Firm Central 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 fromFirm Central
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 Firm Central 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

Firm Central to NetDocuments: what firms ask

Firm Central has shut down. Is it too late to move our data?

Not if the firm ran the exports. Thomson Reuters gave firms a way to download contacts, matters, notes, tasks, calendar events and documents before the product ended. Those files can be cleaned and loaded into a current system. If no export was taken, what remains is whatever was also saved elsewhere.

We exported everything in 2024 but never loaded it anywhere. What can be done with it?

Quite a lot. The CSV files are joined back into matters with their contacts, notes and tasks, and the document bundles are unzipped and filed against the right matter. Before anything is made final, the firm sees a trial load and a list of whatever could not be matched.

Where did our time and billing records go?

They were never in the main Firm Central database. Time & Billing was an eBillity product offered through Thomson Reuters. Firms that kept it moved to a direct arrangement with eBillity. Those that did not would have downloaded invoices and reports before the end, and those downloads are the record.

Do trust balances in Firm Central have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Firm Central 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 NetDocuments has no place for?

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

Matters are carried with mapping, so each mapping is agreed with you first. Emails, tasks, custom fields, 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

Firm Central and NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from Firm Central 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.