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

Data migration route

Actionstep to SharePoint migration

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

FromActionstepCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Tasks: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
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
  • 1 carried
  • 8 mapped
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Actionstep to SharePoint

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

Records in Actionstep and their place in SharePoint
RecordIn ActionstepIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter has a matter type, a workflow step, a system Matter ID and a free-text File Reference.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 referrersHeldJoined to matters as participants, each with a participant type.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldBuilt-in document management, with default folders set per matter type.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to matters through the Outlook add-in.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 notesHeldFile notes on each matter.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldHas a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow steps.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and disbursements.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldCalled client accounting in the UK.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger on the accounting edition; a Xero integration is also offered.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldData collections per matter type, single-row or multi-row, plus participant custom data.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument and email templates with merge fields.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake, CRM and marketing features are part of the platform.No placeKept as a readable archive

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against Actionstep.
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.
Kept as a readable archive
SharePoint has no place for it. It is exported in a format that opens without Actionstep 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 Actionstep 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 Actionstep.

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

Where the data is now

A move off Actionstep starts with how the firm configured it, because two Actionstep firms rarely look alike. Matter types, participant types and data collections were all set up by someone, and each needs a home in the new system. The accounting question comes next: whether the firm’s ledger lives in Actionstep or in Xero changes what has to move at cutover.

  1. Two numbers on every matter

    Actionstep gives each matter a system Matter ID and also has a free-text File Reference. Some firms quote the ID to clients, others the reference, and older matters may show both in use. We record both for every matter, load the one the firm actually uses as the matter number, and keep the other in a searchable field.

  2. Participant types are firm-defined

    Contacts are attached to matters as participants, each with a participant type. The list comes with defaults, but firms add their own, such as trustee, executor or insurer. A destination with a short fixed list of roles cannot take forty participant types as they are, so each one is mapped to a role, a relationship or a custom field.

  3. Multi-row data collections

    Custom fields live in data collections tied to a matter type. A single-row collection maps to ordinary custom fields. A multi-row collection is a table, such as a list of a debtor’s assets, and few systems have a field that holds a table. Those rows usually come across as a note or a document on the matter.

  4. Workflow steps and their history

    Every matter sits at a step in its matter type’s workflow, and Actionstep keeps a history of who completed each step and when. The current step usually maps to a stage or status in the new system. Most products have no equivalent for the step history, so the firm decides whether it is kept as a note.

  5. Where the firm’s books are

    Actionstep can run the general ledger itself or pass accounting entries to Xero. If the ledger is inside Actionstep and the new system has none, the firm is also choosing an accounting package, and opening balances have to be agreed for it. When Xero already holds the books, that part of the move is a reconnection.

More about moving off Actionstep

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

Actionstep to SharePoint: what firms ask

Can we keep our Actionstep matter numbers in the new system?

Usually, if the new system accepts a matter number supplied on import. First we settle which number the firm means: the system Matter ID or the File Reference. The one in daily use becomes the matter number, and the other is kept in a field or note so old correspondence can still be traced.

Our general ledger is in Actionstep. Does it move too?

The ledger does not move as a ledger. What moves is a set of opening balances, agreed with the firm’s accountant at the cutover date, into the new system or into an accounting package beside it. Transaction history stays in the read-only Actionstep copy or in exported reports. Which package holds the books is decided in the analysis.

What happens to our data collections?

Single-row collections map to custom fields where the new system has them. Multi-row collections are tables, and they are harder. Depending on the destination they become repeated records, a note on the matter or a saved document. The firm sees the proposed treatment for each collection before the trial load.

Do trust balances in Actionstep have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Actionstep 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 Actionstep 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 Actionstep data is loaded into SharePoint?

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

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

Moving from Actionstep 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.