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

Data migration route

Insight Legal to SharePoint migration

Insight Legal is a server-based 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.

FromInsight LegalServer
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Emails: Carried with mapping
  4. Calendar: Carried with mapping
  5. Tasks: Carried with mapping
  6. Templates: Carried with mapping
  7. Contacts: Confirmed in the analysis
  8. Notes: 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
  4. Firm accounts: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 5 mapped
  • 4 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Insight Legal to SharePoint

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

Records in Insight Legal and their place in SharePoint
RecordIn Insight LegalIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA central matter record with correspondence history, key dates and next steps.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 referrersTo be confirmedHas a place in partOnly as rows in a list built for the purpose.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldStored in Insight’s cloud, on the firm’s own server, or a mix of both.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldOutlook integration files correspondence to the matter.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
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 deadlinesHeld in partKey dates are saved through the Outlook integration.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow tasks with reminders and escalations.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldBuilt-in time recording.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldClient accounting under the accounts rules of each UK and Irish jurisdiction.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldPurchase ledger, management accounts and Making Tax Digital VAT submission.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 automationHeldPre-built document and email templates with integrated merge fields.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 Insight Legal.
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 Insight Legal 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 Insight Legal 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 Insight Legal.

Insight Legal 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. SharePoint 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

Insight Legal holds the firm’s accounts as well as its cases, so a move off it is an accounting project and a case management project at once. The first fact to pin down is where the system lives. Firms run it hosted, on their own server or half and half, and the documents may be in a different place from the database.

  1. Find the documents first

    Insight lets a firm choose where documents are stored: its cloud storage, the firm’s own server, or a mixture. Older matters may be on a server in the comms cupboard while newer ones are hosted. We confirm each location and check that the paths in the database open real files before any document work is planned.

  2. Accounts rules by jurisdiction

    The accounts package is configured differently for Scotland, England and Wales, Northern Ireland and the Republic of Ireland. A firm’s client ledgers follow one of those rule sets. The destination has to support the same jurisdiction’s rules, and a firm leaving for a product built in another country should confirm that before anything else.

  3. Client money has UK names

    What Australian and American systems call trust, Insight calls client account, and time is recorded by fee earners. The ledgers themselves are the same thing under another name. Reports are another matter: reconciliations and compliance checks produced by Insight are kept as PDFs for the firm’s reporting accountant, since the new system will not regenerate them.

  4. VAT and the purchase ledger

    Office-side accounting runs in Insight too, including a purchase ledger and VAT returns submitted to HMRC through Making Tax Digital. Cutover is easiest at a VAT period end. Unpaid supplier invoices are listed and re-entered in whichever package takes over the office books, and submitted returns stay in the archive.

  5. Workflows are the firm’s own

    Case workflows can be used as supplied or built for the firm, with tasks, prompts and escalations. They do not transfer to another product. During the analysis each workflow in use is written out step by step, with its document templates, so the equivalent can be set up and tested before staff rely on it.

More about moving off Insight Legal

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

Insight Legal to SharePoint: what firms ask

We host Insight on our own server. Does that change the migration?

It changes how the data is collected, not what is moved. With an on-premise installation the database and documents are copied from the firm’s server with its IT provider. With the hosted service we work from what Insight supplies. A split set-up needs both, and the two copies are taken on the same day.

Can the move happen mid-year?

It can, but the accounts side is simpler at a period end. Client ledger balances can be loaded at any agreed date once reconciled. Office accounts are cleaner if the VAT quarter and the purchase ledger are closed first. Most firms pick a month end, and some wait for the financial year end.

Do our client ledgers keep their history?

Balances are loaded for each client and matter and reconciled to Insight’s closing reports. The postings behind them normally remain in the archived system, because another product will not accept them as live entries. Statements and ledger cards for open matters can be saved to each file as PDFs.

Do trust balances in Insight Legal have a place in SharePoint?

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

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

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

Moving from Insight Legal 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.