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

Data migration route

Filevine to Actionstep migration

Filevine is a cloud case management system, and Actionstep is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Actionstep, often from a separate accounts package.

FromFilevineCloud
  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 across
  9. Trust money: Carried across
  10. Intake: Carried across
  11. Billing: Carried with mapping
  12. Custom fields: Carried with mapping
  13. Templates: Carried with mapping
  14. Firm accounts: Confirmed in the analysis
ToActionstepCloud
  • 10 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Filevine to Actionstep

Each row is a kind of record Filevine holds, whether Actionstep 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 is confirmed in the analysis.

Records in Filevine and their place in Actionstep
RecordIn FilevineIn ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled projects. Each has a project type, a phase and sections.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldContact cards, collected on each project’s Contacts section.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldDocs section per project, with folders, named versions and searchable text.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeldProject emails are stored in the activity feed.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesHeldNotes are posted to the activity feed.Has a placeThe import tool has a file notes template.Carried across
CalendarAppointments, court dates and deadlinesHeldDeadlines, deadline chains and project calendars.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks in the activity feed. Phases can create auto-tasks.Has a placeThe import tool has a tasks template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTimekeeping is part of Billing, which must be enabled for the firm.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments through the Billing and Payments products.Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partPayments by Filevine includes trust accounts and a trust reconciliation report.Has a placeTrust balances load per matter through the trust accounts import.Carried across
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeOpening balances are entered against the general ledger, or the books stay in Xero.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom sections and fields are built in the Customs Editor.Has a placeData collections are built per matter type before values are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument generation templates that fill from project data.Has a placeRebuilt as Actionstep templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled by Lead Docket, a separate Filevine product.Has a placeCarried across

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Actionstep brings those two sources together. The case records come from Filevine. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Actionstep, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Where the data is now

No two Filevine set-ups are alike, because each firm designs its own project types and sections. A move off it starts by reading that design: every section, every field, and how many projects actually use them. Much of the firm’s history is in the activity feed as a single stream, and the plan has to say what happens to that.

  1. Sections are the data model

    Static sections hold one set of fields per project. Collection sections hold many items, each with its own fields, such as a row per medical provider. They extract as separate tables. Each one is mapped to a destination record, a set of custom fields or a document, and the firm sees which before the trial load.

  2. The activity feed

    Notes, emails, texts, faxes, reminders and tasks all live in one feed per project, and firms tag them with hashtags. Most systems keep those things in different places. Items are split by type on the way out, so emails become emails and tasks become tasks, with the original date and author kept on each.

  3. Phases and auto-tasks

    A project’s phase can trigger automatic tasks through taskflows. The phase itself maps to a status or stage. Automation does not move, and open auto-tasks are loaded as plain tasks so work in progress still shows on someone’s list. Workflows are then rebuilt in the destination from the firm’s own list of what each phase should trigger.

  4. Archived projects still exist

    Projects cannot be deleted, only moved to the Archived phase, where they drop out of searches and reports unless specifically included. An extract that follows the default view will miss them. Archived projects are counted on their own, and the firm decides how many years of them the new system should hold.

  5. Hashtags instead of folders

    Many firms organise documents and notes with hashtags as much as with folders. A destination built on folders or categories has nowhere obvious for a tag. The most used tags are listed with counts, and each becomes a folder, a document category or text in the name, so a search for it still finds the item.

More about moving off Filevine

Where it is going

Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.

  1. Matter types before any data

    A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.

  2. Old numbers go to File Reference

    Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.

  3. Check before anyone edits

    The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.

  4. Folders come from the matter type

    Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.

  5. Opening balances can be locked

    Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.

More about moving into Actionstep

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 Filevine holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. 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 Filevine, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Filevine are frozen for an agreed window, the data is collected a final time and Actionstep 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. Filevine 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 Filevine 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 fromFilevine
Moving toActionstep

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

    What is in it, how its records link, and where each piece would sit in Actionstep. 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 Actionstep

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

Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.

Set-up decisions in Actionstep

  • Matter types, with workflow steps and default document folders
  • Participant types and data collections for each matter type
  • Document and email templates rebuilt with Actionstep merge fields
  • Trust accounts, chart of accounts and the optional Xero link
  • System roles and data permissions for each group of staff
  • Outlook add-in, divisions and the firm’s billing preferences

Questions

Filevine to Actionstep: what firms ask

Can we take our custom sections with us when we leave?

The data in them, yes. Every static and collection section extracts as fields and rows. The section design itself belongs to Filevine and has to be recreated in whatever the destination offers. Sections that hold only a handful of records are usually better turned into notes than rebuilt.

What happens to everything in the activity feed?

It is separated by type. Notes become file notes, emails become emails where the destination stores them, texts become notes or a transcript, and tasks become tasks. Dates and authors are kept, and hashtags are carried in the text. The count of feed items per project is checked against the load, and any shortfall is listed.

We are moving to Filevine. Do matter numbers carry over?

The old matter number can be kept on the project, in the project name, a number field or both, so that paper files and old correspondence still match. Filevine also gives each project its own ID. Staff are told which number to quote, and searches are tested for the old one.

Do trust balances in Filevine have a place in Actionstep?

Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. Balances are loaded by matter and agreed to the trust report from Filevine as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.

Does everything in Filevine have a place in Actionstep?

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 Actionstep is kept as a readable archive, and you see which before the move.

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

Billing records, custom fields and templates 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

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

Moving from Filevine to Actionstep?

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

We reply within one business day.