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

Data migration route

SurePoint Finance Enterprise data to Microsoft SQL Server

SurePoint Finance Enterprise is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what SurePoint Finance Enterprise holds and keeps it readable and open to queries.

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

What moves

What moves from SurePoint Finance Enterprise to Microsoft SQL Server

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

Records in SurePoint Finance Enterprise and their place in Microsoft SQL Server
RecordIn SurePoint Finance EnterpriseIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, tracked from intake through billing and collections.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldClient and matter contacts; marketing contacts may be in the separate SurePoint CRM.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partAs files in folders with an index table; storing files in the database is possible.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets are part of the system.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows with assignee, due date and status.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldPaperless pre-bill edits, billing rules, LEDES e-billing and matter budgets.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldHas a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable and cost recovery, for one or several entities.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedent files can be stored; automation does not run here.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partThe vendor describes matter intake; lead tracking sits in the separate CRM product.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against SurePoint Finance Enterprise.
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

Not a new system. A complete copy the firm can query.

Writing SurePoint Finance Enterprise out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in SurePoint Finance Enterprise as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

SurePoint Finance Enterprise is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What SurePoint Finance Enterprise will release depends on its export tools, and that is confirmed in the analysis.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what SurePoint Finance Enterprise holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything SurePoint Finance Enterprise holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against SurePoint Finance Enterprise: record counts, totals where SurePoint Finance Enterprise holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in SurePoint Finance Enterprise, the export is run a final time and checked again. There is nothing to go live. SurePoint Finance Enterprise is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

SurePoint Finance Enterprise to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from SurePoint Finance Enterprise?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in SurePoint Finance Enterprise as at the export date.

Does everything in SurePoint Finance Enterprise have a place in Microsoft SQL Server?

Most of it does on paper. Documents, emails, notes, tasks, custom fields and templates 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before SurePoint Finance Enterprise is written out to Microsoft SQL Server?

Documents, emails, notes, tasks, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from SurePoint Finance Enterprise to Microsoft SQL Server?

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

We reply within one business day.