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

Data migration route

Actionstep data to SQLite

Actionstep is a cloud practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Actionstep holds and keeps it readable and open to queries.

FromActionstepCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Firm accounts: Exported in full
  10. Intake: Exported in full
  11. Documents: Exported with mapping
  12. Emails: Exported with mapping
  13. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 10 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Actionstep to SQLite

Each row is a kind of record Actionstep holds, whether SQLite has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.

Records in Actionstep and their place in SQLite
RecordIn ActionstepIn SQLiteWhat 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 placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldJoined to matters as participants, each with a participant type.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldBuilt-in document management, with default folders set per matter type.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
EmailsEmails saved to matters or to the storeHeldSaved to matters through the Outlook add-in.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldFile notes on each matter.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldHas a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow steps.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and disbursements.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldHas a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldCalled client accounting in the UK.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger on the accounting edition; a Xero integration is also offered.Has a placeLedger journals as rows, where the source held them.Exported in full
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 added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument and email templates with merge fields.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake, CRM and marketing features are part of the platform.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Actionstep.
Exported with mapping
SQLite 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
SQLite 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

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

Writing Actionstep out to SQLite 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 Actionstep 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.

Actionstep is hosted by its maker and SQLite 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 Actionstep will release depends on its export tools, and that is confirmed in the analysis.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

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 Actionstep holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Actionstep 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 SQLite as a trial and checked against Actionstep: record counts, totals where Actionstep 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 Actionstep, the export is run a final time and checked again. There is nothing to go live. Actionstep 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 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 toSQLite

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

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

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

Actionstep to SQLite: 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.

Does the copy in SQLite hold trust ledgers from Actionstep?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Actionstep as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. 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

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

Moving from Actionstep to SQLite?

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

We reply within one business day.