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

Data migration route

LawBase to SurePoint Finance Enterprise migration

LawBase is a case management system, and SurePoint Finance Enterprise is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SurePoint Finance Enterprise, often from a separate accounts package.

FromLawBaseCase management
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Calendar: Carried across
  4. Documents: Confirmed in the analysis
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
  8. Time and expenses: Confirmed in the analysis
  9. Billing: Confirmed in the analysis
  10. Trust money: Confirmed in the analysis
  11. Firm accounts: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToSurePoint Finance EnterpriseCloud
  • 3 carried
  • 11 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawBase to SurePoint Finance Enterprise

Each row is a kind of record LawBase holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route three kinds of record carry across and eleven kinds are confirmed in the analysis.

Records in LawBase and their place in SurePoint Finance Enterprise
RecordIn LawBaseIn SurePoint Finance EnterpriseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldScreens and fields are designed per office and practice area.Has a placeCarried across
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.Has a placeCarried across
DocumentsFiles stored in or linked from the systemTo be confirmedTo be confirmedConfirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.Has a placeCalendar entries and dockets.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger and payables, by entity.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe whole database layout is defined by the office.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.To be confirmedConfirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedTo be confirmedConfirmed in the analysis

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SurePoint Finance Enterprise brings those two sources together. The case records come from LawBase. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SurePoint Finance Enterprise, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

How LawBase 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. LawBase 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. SurePoint Finance Enterprise 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

No two LawBase databases are the same, because each office designed its own screens and fields. A move off it starts with reading that design: what tables exist, what each field means in this office, and which are still used. Offices that have run it for decades also hold very long case histories, and the retention decision is made early.

  1. A database the office designed

    LawBase lets an office lay out its own screens and choose its own fields for each practice area. A field labelled Adjuster or Docket Number exists because someone asked for it. There is no standard layout to map from. We document the one in use, with the office’s own people explaining what each field has come to mean.

  2. SmartFolders are groupings

    SmartFolders group files automatically by attorney, subject or any other value in the system. They behave like saved searches, not containers, so there is nothing in them to move. The useful ones are recreated as saved views or reports in the destination, once the fields they depend on have been loaded.

  3. HotDocs templates

    Document assembly runs through HotDocs, and producing a document can also create notes and tasks. The templates are HotDocs files with their own variables and logic. If the destination also works with HotDocs, they may be reused with remapped variables. Otherwise each template is rebuilt in the new system’s own tool.

  4. File room records

    LawBase is used for file room management, tracking physical files as well as electronic records. Those entries say where a paper file is. Few cloud systems have a file room module. The location data is brought across in custom fields, or exported as a register for whoever looks after the firm’s storage.

  5. Workflow fired by field changes

    Changing a single field can trigger an email, a document, other field updates, a note or calendar tasks. Over the years offices build many of these rules. They are listed during the analysis, because staff often no longer know which steps the system does for them until the new one fails to do it.

More about moving off LawBase

Where it is going

Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.

  1. Entities and tax IDs first

    The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.

  2. History has to balance

    Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.

  3. E-billing detail on time entries

    For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.

  4. Dockets as well as appointments

    Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.

  5. Cost recovery codes

    Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.

More about moving into SurePoint Finance Enterprise

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in SurePoint Finance Enterprise, they get a rehearsed cutover of their own.

  1. Analysis

    We read what LawBase holds and how it is organised, then agree with you where each kind of record will sit in SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise and checked against LawBase: 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

    After a short freeze on changes in LawBase, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. LawBase 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 LawBase 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 fromLawBase
Moving toSurePoint Finance Enterprise

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

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

Loaded data is not yet a working system. This is what NewLaw sets up in SurePoint Finance Enterprise, beyond the migration, so that people can work in it from the first day.

The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.

Set-up decisions in SurePoint Finance Enterprise

  • Entity structure, tax IDs and the chart of accounts
  • Bank and trust accounts with reconciliation set-up
  • Timekeeper rates, classifications and task code sets
  • Pre-bill approval steps and client billing rules
  • LEDES e-billing formats for each corporate client
  • Management and compensation reports the partners use

Questions

LawBase to SurePoint Finance Enterprise: what firms ask

Our LawBase has thirty years of cases. Do they all move?

They can, but the office does not have to take them all. Open matters and those inside the retention period move as full records. Older ones can come across as a summary record with notes, or remain in the LawBase database kept read only. The office’s retention policy and how often old files are consulted decide the line.

Does LawBase hold our billing?

The vendor’s material describes case, matter and practice management and does not describe a billing ledger, so we do not assume one. If your office records time or costs in LawBase fields it designed, those are found in the analysis. Any separate billing system is scoped as its own source.

Can our custom screens be recreated?

The fields can, where the destination supports custom fields by matter type. Exact screen layouts usually cannot, and they are rarely worth chasing. We agree with each practice group which fields they still need on screen, load the rest where they can be reported on, and drop fields that have sat empty for years.

Do trust balances in LawBase have a place in SurePoint Finance Enterprise?

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 LawBase before the plan is fixed. If SurePoint Finance Enterprise turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in LawBase have a place in SurePoint Finance Enterprise?

Most of it does on paper. Documents, emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.

What has to be decided before LawBase data is loaded into SurePoint Finance Enterprise?

Documents, emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields, templates 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

LawBase and SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.

Moving from LawBase to SurePoint Finance Enterprise?

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

We reply within one business day.