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

Data migration route

PerfectLaw to NetDocuments migration

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

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

What moves

What moves from PerfectLaw to NetDocuments

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

Records in PerfectLaw and their place in NetDocuments
RecordIn PerfectLawIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases are managed in AIM, the Attorney’s Information Manager.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 referrersHeldParties are related to matters by defined relationships for conflict checks.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldIts own document management system; reports can be profiled into it.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail profiling tools are listed among its applications.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeldNo placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldIncludes collections and billing compliance tools.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust history by matter within client, for each trust account.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger and accounts payable, with profit centres.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 automationHeldForms and document assembly.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 pipelinesHeld in partA matter intake workflow for opening new matters.No placeKept as a readable archive

What the plans mean

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

PerfectLaw 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

PerfectLaw is one database doing the work of four or five products. A firm leaving it is replacing its case management, document store, billing, general ledger and accounts payable at once, often with two or three separate systems. The plan has to say which destination takes which part, and how the links between them, especially client and matter numbers, are kept.

  1. One source, several destinations

    Front office and back office share a database. If the firm is moving to a practice management system plus a separate accounting package, the single source is split in two. Client and matter identifiers must be identical in both destinations, so they are fixed first and every extract is keyed on them.

  2. Matter within client

    Trust history is kept by matter within client, and the rest of the system follows the same client and matter structure. A destination that numbers matters independently of clients needs a rule for combining the two. We settle that rule with the accounts team, since their reports and bank records use the existing numbers.

  3. Scanned invoices and cheques

    The accounts payable side can store scanned supplier invoices and images of signed cheques, linked to vendors, matters and clients. These are financial records, not matter documents. They are counted separately and usually go to the accounting package or a finance archive, with the link to the vendor kept in the file name or index.

  4. Records management by barcode

    PerfectLaw lists records management with barcodes among its front office applications, for tracking physical files. If the firm uses it and the new system has no records module, the file locations are loaded into custom fields on the matter or handed to the records team as a register.

  5. A segmented general ledger

    The general ledger uses multi-segment account numbers and can distribute overhead among profit centres. An accounting package with a flat chart of accounts needs those segments translated into its own tracking categories or classes. The firm’s accountant agrees the new chart before opening balances are prepared.

More about moving off PerfectLaw

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

PerfectLaw to NetDocuments: what firms ask

Can everything in PerfectLaw go into one new system?

Sometimes, if the destination includes full accounting. More often the firm ends up with a practice management system and an accounting package, and perhaps a document management system. The analysis lists every PerfectLaw function the firm uses and shows which destination covers it, so nothing is assumed.

What happens to documents in the PerfectLaw DMS?

They are extracted with whatever profile data the document store keeps for them, such as client and matter. In the destination each document is filed to its matter, into a folder derived from the profile where folders are used. Reports that were profiled into the document store are identified, since most are not matter documents.

We are in PerfectLaw’s hosted cloud. Does that change anything?

It changes who provides the copy. A firm with its own server gives us access with its IT provider. A firm in the vendor’s hosted environment asks the vendor for the database and documents. The checks afterwards are the same, and a read-only copy still needs a home once hosting ends.

Do trust balances in PerfectLaw have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from PerfectLaw 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, the firm’s accounts and intake records. They are exported from PerfectLaw 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 PerfectLaw data is loaded into NetDocuments?

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

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

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