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

Data migration route

Docketwise to NetDocuments migration

Docketwise is a cloud case management system for immigration work, 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.

FromDocketwiseCloud
  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. Firm accounts: 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. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 3 mapped
  • 2 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Docketwise to NetDocuments

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

Records in Docketwise and their place in NetDocuments
RecordIn DocketwiseIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration matters with status, priority dates, expiry dates and receipt tracking.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 and the people related to their matters, plus leads.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldKept against clients and matters; filing packages are assembled from forms and documents.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 can be sent from inside the product; Gmail and Outlook are integrations.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 deadlinesHeldAppointments and deadlines; Google Calendar and Outlook are integrations.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks, with task and email automations.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime tracked against matters, alongside flat-fee charges.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, saved charges, payment plans and reminders; payments through LawPay.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust requests, per-client balances and filing-fee disbursements.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesTo be confirmedInvoices, payments and trust transactions sync to QuickBooks on some plans.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom attributes on contacts and matters.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldGovernment form library, questionnaires and reusable email templates.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 pipelinesHeldLeads from the website, Facebook Messenger, WhatsApp and SMS in one dashboard.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 Docketwise.
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 Docketwise 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 Docketwise 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 Docketwise 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 Docketwise 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 Docketwise is kept running until the checks on NetDocuments are finished.

Where the data is now

Docketwise keeps one set of answers for each client and builds every form from it. A firm leaving has two different jobs. The practice records, meaning matters, time, invoices and trust, move much as they would from any system. The immigration records, meaning questionnaire answers, form data and case status tracking, only have a home if the destination is also built for immigration work.

  1. One questionnaire, many forms

    A single intake questionnaire can combine several immigration forms, and the client’s answers fill all of them. The answers are held as data against the client. In the analysis each answer is matched to a field in the new system. Where there is no match, the completed forms are kept as PDFs so the filed version is still on the matter.

  2. Trust is kept per client

    The product describes trust as per-client balances, with trust requests and filing-fee disbursements. Many practice systems hold trust per matter. A client with two open matters and one trust balance needs a rule for where the money sits after the move, and the firm sets that rule before the financial cutover is rehearsed.

  3. Flat fees and payment plans

    Immigration work is mostly billed as flat fees, and Docketwise handles that with saved charges and payment plans that debit the client through LawPay on a schedule. Part-paid plans are the awkward records. Each one is listed with what has been paid and what is still due, and the instalments are rebuilt in the new system.

  4. USCIS status tracking stops

    Receipt numbers are held on the matter and the product checks USCIS for status changes, then tells the client. The receipt numbers move as ordinary fields. The automatic checking does not, unless the new system does the same thing. Staff need to know before go-live who will be checking case status and how.

  5. Answers in other languages

    Clients can complete questionnaires in their own language, and messages can be translated. Some stored answers will therefore not be in English. The trial load is checked with a few of these clients in particular, because accented characters and non-Latin scripts are where an import most often damages text without anyone noticing.

More about moving off Docketwise

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

Docketwise to NetDocuments: what firms ask

What happens to our LawPay and QuickBooks connections?

LawPay and QuickBooks are separate products that Docketwise connects to, so they are not part of the move itself. Payment history stays in LawPay and the ledger stays in QuickBooks. What changes is the connection, which is set up again from the new system, with opening balances agreed between the two.

Can we keep the completed forms for every client?

Yes. A filed form is the record of what was sent to the government, so it is kept whatever the destination. Each one is saved as a PDF against the matter it belongs to, with its date. The trial load is checked by counting forms per matter against Docketwise for a sample of clients.

Do leads come across, or only clients?

Leads are held in the same system as clients, with their source and any messages. If the new system has an intake pipeline they can be loaded into it. Old leads that never became clients are often left out, and the firm chooses a cut-off date for those during the analysis.

Do trust balances in Docketwise have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Docketwise 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 intake records. They are exported from Docketwise 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 Docketwise data is loaded into NetDocuments?

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

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

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