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

Data migration route

SurePoint Finance Enterprise to NetDocuments migration

SurePoint Finance Enterprise is a cloud practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

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

What moves

What moves from SurePoint Finance Enterprise to NetDocuments

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

Records in SurePoint Finance Enterprise and their place in NetDocuments
RecordIn SurePoint Finance EnterpriseIn NetDocumentsWhat 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 client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClient and matter contacts; marketing contacts may be in the separate SurePoint CRM.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeImported with profile values, folder, dates and access set per document.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets are part of the system.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed 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 placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.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
NetDocuments 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
NetDocuments 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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from SurePoint Finance Enterprise is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces SurePoint Finance Enterprise for matters and billing, or into an archive.

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

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 toNetDocuments

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

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

SurePoint Finance Enterprise to NetDocuments: 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 NetDocuments?

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

On this route that is contacts, calendar entries, 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 NetDocuments?

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

Moving from SurePoint Finance Enterprise to NetDocuments?

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

We reply within one business day.