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

Data migration route

Time Matters to NetDocuments migration

Time Matters is a server-based 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.

FromTime MattersServer
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Tasks: Confirmed in the analysis
  7. Trust money: Confirmed in the analysis
  8. 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
Readable archiveNo place in NetDocuments
  • 2 carried
  • 3 mapped
  • 3 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Time Matters to NetDocuments

Each row is a kind of record Time Matters holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, five kinds have no place in NetDocuments and are archived and three kinds are confirmed in the analysis.

Records in Time Matters and their place in NetDocuments
RecordIn Time MattersIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas 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 referrersHeldNo placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocuments are created, searched and tied to clients and matters.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldEmails and attachments are managed against matters.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeldNotes and phone calls are separate records.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCalled Events.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldCalled ToDos.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partBasic billing; advanced billing in the Billing Matters edition.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldForms, fields and record layouts are set by the firm.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldMerge Templates, AutoEntry Forms, Triggers and Chains.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
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 Time Matters.
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 Time Matters 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 Time Matters 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 Time Matters for matters and billing, or into an archive.

Time Matters 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. NetDocuments 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

Firms that have used Time Matters for years have usually reshaped it, and that is what takes thought when leaving. The standard records, which are contacts, matters, events, to-dos, notes, phone calls, emails and documents, move in a predictable way. What differs in every installation is the firm’s own forms, added fields, Triggers and Chains, and the analysis spends most of its time there.

  1. Forms the firm redesigned

    Record forms, field labels and layouts can be changed by the firm. A field that the default form calls one thing may carry a different label, and a different meaning, on the firm’s version. The mapping is made from the firm’s own form definitions, never from the default names.

  2. Triggers and Chains

    Triggers start tasks or events when a date or status changes, and Chains join steps into a sequence. AutoEntry Forms cut down repeated entry. The records they created come across, but the rules do not, so the processes that still matter are written down with the staff who use them and rebuilt in the destination.

  3. Every record type is separate

    Events, ToDos, phone calls, notes, emails and documents are distinct kinds of record, each tied to a matter or contact. Phone records in particular have no equivalent in many systems, and are loaded as dated notes. Counts for each record type are checked against Time Matters matter by matter.

  4. Billing may be elsewhere

    Time and expenses are recorded here, but invoices and ledgers may be kept in PCLaw or QuickBooks through a link, or in Billing Matters. The move identifies which, and treats that program as a second source. Matters are paired across the two using the reference the link relies on.

  5. Supported versions turn over

    The vendor retires versions on a published schedule, release by release, so a firm that has not upgraded for a few years may be on one that is out of support. It can still be moved. Its backup is checked early, since vendor help with a failed restore may not be on offer for a retired release.

More about moving off Time Matters

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 Time Matters 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 Time Matters: 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 Time Matters, a final pass over a weekend picks up what changed since the trial. Time Matters 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 Time Matters 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 fromTime Matters
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 Time Matters 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

Time Matters to NetDocuments: what firms ask

Do our documents come across with their matter links?

Each document in Time Matters has a record that ties it to a client or matter. The record supplies the matter, description and date, and the file supplies the content. Both are needed. Where a record refers to a file that has been moved or deleted, it is reported before the trial load.

Can we keep our custom fields?

The ones in use, yes, if the destination has custom fields for matters and contacts. Every field the firm added is listed in the analysis with how often it is filled. Fields that held structured data move as fields. Those used as scratch space usually become part of a note, by the firm’s choice.

We link Time Matters to PCLaw. Do they move together?

They should be planned together even if they go live a few days apart. The link keeps clients, matters and time in step between the two, and both feed the new system. One matter list is built from both, with PCLaw as the authority for money and Time Matters for the rest.

Do trust balances in Time Matters have a place in NetDocuments?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Time Matters before the plan is fixed. If NetDocuments turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records NetDocuments has no place for?

On this route that is contacts, notes, calendar entries, time entries and billing records. They are exported from Time Matters 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 Time Matters data is loaded into NetDocuments?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks, trust ledgers 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

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

Moving from Time Matters 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.