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

Data migration route

NetDocuments to Litify migration

NetDocuments is a cloud document management system, and Litify is a cloud case management system. The move is matching each file in NetDocuments to its case in Litify.

FromNetDocumentsCloud
  1. Matters: Carried across
  2. Documents: Carried across
  3. Emails: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Notes: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
ToLitifyCloud
  • 2 carried
  • 3 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from NetDocuments to Litify

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

Records in NetDocuments and their place in Litify
RecordIn NetDocumentsIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partA matter is a profile value, normally with a workspace, and can be marked closed.Has a placeMatters, by case type.Carried across
DocumentsFiles stored in or linked from the systemHeldEach has a unique document ID, a profile and numbered versions, one marked official.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook through ndMail or the Outlook add-in into the matter workspace.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedndThread holds team conversations. Whether a firm uses it is checked in the analysis.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom profile attributes, with lookup tables and parent and child links between them.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as documents. PatternBuilder automation is a separate product.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping

What the plans mean

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

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. NetDocuments organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Litify before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of NetDocuments 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 NetDocuments is kept running until the checks on Litify are finished.

Where the data is now

Everything in NetDocuments is reached through the service, so a move off it is an export: documents and their versions are downloaded, and the profile values, folder paths and access lists are collected alongside as data. The files mean little without that data. A document’s place in a matter comes from its client and matter attributes, not from a folder on a disk.

  1. Profile first, folder second

    A document belongs to a matter because its client and matter attributes say so. Folders inside the workspace are optional, and many documents sit in none. An export that walks folders will miss those. The extraction is driven from the profile, cabinet by cabinet, and folder paths are added where they exist.

  2. Filters and saved searches

    Much of what users see in a workspace is not a folder at all. A filter shows documents with a given attribute, such as document type, and a saved search shows results from anywhere in the cabinet. Neither contains files. The analysis works out which of these views need a real folder in the destination.

  3. The official version

    One version of each document is marked official, and it is not always the latest. Version numbers are never reused, so a document can have versions 1 and 3 with no 2. The firm chooses between taking every version or the official one only, and the choice can differ for open and closed matters.

  4. Document IDs appear in footers

    Every document has a unique document ID that firms stamp into footers and quote in correspondence. The destination will number documents its own way. Carrying the old ID across as a field the new system can search, or as part of the name, lets someone holding a five-year-old letter still find the document it refers to.

  5. Access lists and external users

    Access is set per item as view, edit, share and administer rights for users and groups, and cabinets can include external members and CollabSpaces shared with clients. Internal restrictions are mapped to the destination’s security. What outside parties could see is listed separately, because that sharing ends when the cabinet does.

More about moving off NetDocuments

Where it is going

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in NetDocuments and checking each trial against NetDocuments.

  1. Analysis

    We read what NetDocuments holds and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify and checked against NetDocuments: 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 NetDocuments, a final pass over a weekend picks up what changed since the trial. NetDocuments 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 NetDocuments 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 fromNetDocuments
Moving toLitify

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 NetDocuments holds

    What is in it, how its records link, and where each piece would sit in Litify. 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 Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

NetDocuments to Litify: what firms ask

Can we export everything from NetDocuments ourselves?

Partly. NetDocuments provides ndWeb Export, which lets authorised users export documents to a location an administrator has approved. That suits a matter or a client. A whole cabinet with versions, profile data and access lists needs a planned extraction, and the counts are checked against the cabinet afterwards.

Will our document IDs survive the move?

Not as live identifiers. The document ID belongs to NetDocuments and the next system numbers documents its own way. The old ID can be carried as a field or in the document name, so that references in footers, emails and bundles can still be looked up. Links pasted into documents point at NetDocuments, not at the new system.

What happens to documents nobody profiled properly?

They are found in the analysis: documents with no matter, or filed to a general or miscellaneous matter. The firm gets a list with counts by author and date. Some can be assigned by rule, for example from the folder they sit in. The rest are loaded to a holding area or left in the read-only copy.

Do documents from NetDocuments keep their folders and dates in Litify?

Litify stores documents. Loaded to the document component and attached to matters. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in NetDocuments have a place in Litify?

Most of it does on paper. Notes and tasks could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.

What has to be decided before NetDocuments data is loaded into Litify?

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

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

Moving from NetDocuments to Litify?

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

We reply within one business day.