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

Data migration route

SurePoint Finance Enterprise to SharePoint migration

SurePoint Finance Enterprise is a cloud practice management system, 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.

FromSurePoint Finance EnterpriseCloud
  1. Matters: Carried with mapping
  2. Contacts: Carried with mapping
  3. Calendar: Carried with mapping
  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. Custom fields: Confirmed in the analysis
  9. Templates: 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. Firm accounts: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 3 mapped
  • 6 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from SurePoint Finance Enterprise to SharePoint

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

Records in SurePoint Finance Enterprise and their place in SharePoint
RecordIn SurePoint Finance EnterpriseIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, tracked from intake through billing and collections.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 referrersHeldClient and matter contacts; marketing contacts may be in the separate SurePoint CRM.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiles in libraries, with columns and versions.Confirmed in the analysis
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 notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets are part of the system.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a place in partPossible as a list; no legal workflow built in.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldPaperless pre-bill edits, billing rules, LEDES e-billing and matter budgets.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldNo placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable and cost recovery, for one or several entities.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 automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partThe vendor describes matter intake; lead tracking sits in the separate CRM product.No placeKept as a readable archive

What the plans mean

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

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

Where the data is now

A firm on LMS may have been on it for a long time, and the system then holds its financial memory: bills, payments, cheques and journals going back years. Leaving means deciding how much of that memory travels and how the rest stays available. It also means replacing a general ledger and payables system, which makes the finance team the main party to the project.

  1. Which SurePoint product

    The SurePoint name covers several different systems: Finance Enterprise, which is LMS, Finance Core, which is Coyote, and the newer SurePoint Pro. Staff often just say SurePoint. The licence and the vendor’s support listing settle which one the firm runs, and that is confirmed before any method is chosen.

  2. Decades of ledger history

    LMS grew out of a specialist accounting package from Rippe & Kingston, and long-standing firms carry history from each stage. Old matter numbering schemes and timekeepers who left years ago are still referenced by live records. The analysis sets a cut-off year and shows what falls on each side of it.

  3. Several entities, one system

    Finance Enterprise supports multi-entity firms and multiple tax IDs within one system. A destination may need a separate set of books for each entity. The entity that owns each matter, bank account and vendor bill is established first, since intercompany balances have to agree on both sides at cutover.

  4. Billing rules for each client

    Built-in billing rules and e-billing support are used to stop invoices being rejected by corporate clients. Those rules were entered over years and are seldom written down anywhere else. They are extracted as a list for each client, and the first e-bills from the new system are checked against them.

  5. Reports the partners rely on

    With several hundred standard reports and custom dashboards, each firm has its own handful that drive compensation and management meetings. Reports do not migrate. The firm names the ones it cannot do without, and each is reproduced from the trial load and compared with the LMS original.

More about moving off SurePoint Finance Enterprise

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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise, a final pass over a weekend picks up what changed since the trial. SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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 fromSurePoint Finance Enterprise
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 SurePoint Finance Enterprise 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

SurePoint Finance Enterprise to SharePoint: what firms ask

Is SurePoint LMS the same as SurePoint Finance Enterprise?

Yes. SurePoint’s own site labels Finance Enterprise as formerly LMS, and its support pages list it as SurePoint Finance Enterprise (LMS). It is a different system from Finance Core, which was Coyote Analytics, and from SurePoint Pro. A firm should confirm which one it holds before planning a move.

Where are our documents if we use LMS?

That varies by firm and we would not assume. The vendor describes pairing its practice and accounting products with separate document applications, so many firms keep documents in a dedicated document management system. Where each matter’s documents are held, and whether they need to move at all, is recorded in the analysis.

How much financial history should we take with us?

Enough to answer the questions the firm is really asked: open receivables with their invoices, trust ledgers, unbilled time, and usually a few years of billing by client and matter. Older detail stays in the read-only copy of LMS. The cut-off is agreed with the finance partner during the analysis.

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

No. SharePoint does not keep trust ledgers. Trust records from SurePoint Finance Enterprise 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, the firm’s accounts and intake records. They are exported from SurePoint Finance Enterprise 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 SurePoint Finance Enterprise data is loaded into SharePoint?

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

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

Moving from SurePoint Finance Enterprise 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.