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

Data migration route

Bill4Time to SharePoint migration

Bill4Time is a cloud accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromBill4TimeCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Notes: Carried with mapping
  5. Calendar: Carried with mapping
  6. Tasks: Carried with mapping
  7. Templates: Carried with mapping
  8. Emails: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
  10. Intake: 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
Readable archiveNo place in SharePoint
  • 1 carried
  • 6 mapped
  • 3 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Bill4Time to SharePoint

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

Records in Bill4Time and their place in SharePoint
RecordIn Bill4TimeIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe level under a client; firms may label it matter, case, project or engagement.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, with the contacts recorded under each.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldFiles stored against contacts and matters; Box and NetDocuments can be connected.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
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 deadlinesHeld in partScheduled items sync with Google Calendar or Outlook Calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldHas a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses with custom rates, expense categories and billing codes.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBatch invoicing, LEDES, payment plans and write-offs.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldOperating and trust funds are kept apart on invoices and reports.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice templates; document templates were not confirmed.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

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

An export the firm can open without the system.

SharePoint holds files, and most of what Bill4Time holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Bill4Time, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.

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

Where the data is now

Most of what a firm has built up in Bill4Time is financial: years of time entries, invoices, payments and trust movements, coded the way its clients require. A move off it is judged by whether those figures arrive intact and still add up by client and matter. The practice management records around them are usually thinner and take less of the effort.

  1. Billing codes clients expect

    Firms that bill insurers or corporate clients set up billing codes and expense categories so that LEDES invoices are accepted. Those code lists are the firm’s own. They are extracted as reference data and matched to the destination’s codes before any time entry is loaded, since an unmatched code can cause an e-billing rejection later.

  2. QuickBooks already has copies

    The connector has been sending invoices and payments to QuickBooks, where clients appear as customers. If the new system also posts to that QuickBooks file, it must be told about the existing customers and open invoices. Otherwise the first sync creates a second set. The accountant agrees the mapping before go-live.

  3. Client first, then matter

    Everything is filed under a client and then a matter, and firms rename that second level to suit themselves. A consultancy arm may call it a project. The analysis records the label in use and checks whether non-legal projects are mixed in with matters, because they may not belong in a legal system.

  4. Calendars synced with Outlook

    Where the Google Calendar or Outlook Calendar connection is switched on, scheduled meetings, tasks and time entries pass between the two. Those appointments already exist in the mail system, which is not changing, so they are not loaded twice. Deadlines kept only as Bill4Time tasks are the items that need to be carried across.

  5. Rates for past and future

    Bill4Time lets a firm set its own rates alongside its expense categories and billing codes. When time is loaded into a new system the historic entries keep the rate they were billed at. The rate tables for future work are a separate job, rebuilt in the destination and tested by raising a draft invoice on a known matter.

More about moving off Bill4Time

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

Bill4Time to SharePoint: what firms ask

Can we bring all our old invoices, or only what is still owed?

That depends on the destination. Some systems load paid invoices as history. Others accept open balances only, with the old invoices saved as PDFs on each matter. In both cases the debtor total in the new system is checked against the Bill4Time aged receivables report on the cutover date.

We keep documents in NetDocuments, connected to Bill4Time. Do they move?

They can stay where they are. NetDocuments holds the files and Bill4Time only links matters to them. If the new practice system also connects to NetDocuments, the links are re-made matter by matter. Files uploaded directly into Bill4Time are a different case and are extracted with the matter.

How are trust balances moved?

As an opening balance for each client and matter, agreed with the trust bank statement on the day. The transaction history behind each balance moves too where the destination accepts it. A full trial load is done beforehand as a dress rehearsal, because a trust cutover cannot be re-run the way a document load can.

Do trust balances in Bill4Time have a place in SharePoint?

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

Matters, contacts, notes, calendar entries, tasks and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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

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

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