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

Data migration route

Docketwise to SharePoint migration

Docketwise is a cloud case management system for immigration work, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from Docketwise to SharePoint

Each row is a kind of record Docketwise holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping, four kinds have no place in SharePoint and are archived and one kind is confirmed in the analysis.

Records in Docketwise and their place in SharePoint
RecordIn DocketwiseIn SharePointWhat 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 site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldClients and the people related to their matters, plus leads.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldKept against clients and matters; filing packages are assembled from forms and documents.Has a placeFiles in libraries, with columns and versions.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 place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldAppointments and deadlines; Google Calendar and Outlook are integrations.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks, with task and email automations.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
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 placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldGovernment form library, questionnaires and reusable email templates.Has a place in partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against Docketwise.
Carried with mapping
SharePoint 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
SharePoint 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Docketwise into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Docketwise.

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 SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 toSharePoint

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

Structure, permissions and handover

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Docketwise to SharePoint: 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 SharePoint?

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Docketwise to SharePoint?

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

We reply within one business day.