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

Data migration route

Liberate to NetDocuments migration

Liberate is a 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.

FromLiberatePractice management
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Templates: Carried with mapping
  5. Contacts: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Calendar: Confirmed in the analysis
  8. Tasks: Confirmed in the analysis
  9. Trust money: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
  11. Intake: Confirmed in the analysis
ToNetDocumentsCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Firm accounts: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 2 mapped
  • 7 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Liberate to NetDocuments

Each row is a kind of record Liberate 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, three kinds have no place in NetDocuments and are archived and seven kinds are confirmed in the analysis.

Records in Liberate and their place in NetDocuments
RecordIn LiberateIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldElectronic matters holding data, documents and emails.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 referrersTo be confirmedNo placeConfirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldTags and definable document categories, with version control.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are held on the matter; time spent in Outlook can be recorded.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partAuthorisation workflows and business process automation.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldIncludes automatic time recording.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldOne-click and scheduled billing, with credit control procedures.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldPurchase ledger, supplier database and built-in financial reporting.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 automationHeldPrecedents and document templates filled with matter data.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 Liberate.
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 Liberate 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 Liberate 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 Liberate for matters and billing, or into an archive.

How Liberate 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. Liberate 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

Linetime sells Liberate to larger firms, which tend to have high matter volumes and an accounts department that runs credit control inside the system. Customisation by Linetime is part of the offer. A move therefore begins with an inventory of what was changed for this firm, and with the accounts team, whose billing schedules, credit control procedures and purchase ledger all have to be closed off or carried over.

  1. Customised for the firm

    Linetime offers customisation to meet a firm’s own needs, and long-standing clients may have screens, fields and processes built for them. Those additions are not in any manual. We ask the firm and the vendor for a list, then confirm it against the database, so a field built only for this firm is not missed.

  2. Categories and tags, not folders

    Documents are organised by tags and by categories the firm defines. A matter’s documents may never have been in a folder. For a destination that files by folder, the category becomes the folder name, tags are carried as metadata where the new system has it, and uncategorised documents are placed in a general folder for review.

  3. Documents under version control

    Liberate keeps documents under version control. A migration normally takes the latest version of each document. Where the firm needs earlier drafts, we establish how Liberate stores them and whether the destination has its own versioning to receive them, then test on a matter with a long drafting history.

  4. Credit control procedures

    Credit control is run inside Liberate, with procedures that can be set at client and matter level. An unpaid bill may be part-way through a chasing sequence at cutover. The debtor balances move as figures. Alongside them, the stage each debt has reached is exported as a list so the accounts team can pick up the chase.

  5. Scheduled bills in progress

    Billing can be scheduled, so some clients are billed automatically on set dates. Those schedules do not transfer. They are listed before cutover with their amounts and dates, the last scheduled run is completed in Liberate, and the equivalent arrangement is set up in the new system before the next one falls due.

More about moving off Liberate

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

Liberate to NetDocuments: what firms ask

How do we find out what was customised for us?

Start with the people who asked for it: accounts, department heads, IT. Linetime’s records of development work for the firm help as well. We then compare the firm’s database with the list, looking for tables and fields that hold data but appear in nobody’s account, and ask what they were for.

Does our purchase ledger move?

Only if the new system, or an accounting package beside it, has a purchase ledger. Supplier records and unpaid supplier invoices are extracted and loaded there as opening items. Paid history stays in the archive. A firm moving to a product without office accounts decides on its accounting package during the analysis.

Can the move be staged by department?

Case data can sometimes be staged. Accounts cannot be split easily, because billing and the ledgers for the whole firm sit in one system. Running two systems also means two places to check conflicts. Most firms move everything in one cutover and stage the training instead.

Do trust balances in Liberate 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 Liberate 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 time entries, billing records and the firm’s accounts. They are exported from Liberate 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 Liberate data is loaded into NetDocuments?

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

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

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