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

Data migration route

Actionstep to Filevine migration

Actionstep is a cloud practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromActionstepCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Intake: Carried with mapping
  14. Firm accounts: Confirmed in the analysis
ToFilevineCloud
  • 7 carried
  • 6 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Actionstep to Filevine

Each row is a kind of record Actionstep holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across, six kinds need mapping and one kind is confirmed in the analysis.

Records in Actionstep and their place in Filevine
RecordIn ActionstepIn FilevineWhat 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 placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldJoined to matters as participants, each with a participant type.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldBuilt-in document management, with default folders set per matter type.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to matters through the Outlook add-in.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldFile notes on each matter.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldHas a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow steps.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and disbursements.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHas a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldCalled client accounting in the UK.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger on the accounting edition; a Xero integration is also offered.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldData collections per matter type, single-row or multi-row, plus participant custom data.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument and email templates with merge fields.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake, CRM and marketing features are part of the platform.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against Actionstep.
Carried with mapping
Filevine 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.

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Actionstep has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Actionstep, and kept as the record of what was billed and held.

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

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Actionstep holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Actionstep, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against Actionstep: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Actionstep are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 toFilevine

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

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

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Actionstep to Filevine: 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 Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Actionstep have a place in Filevine?

Most of it does on paper. The firm’s accounts 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before Actionstep data is loaded into Filevine?

Time entries, billing records, trust ledgers, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

Moving from Actionstep to Filevine?

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

We reply within one business day.