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

Data migration route

Litify to Actionstep migration

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

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

What moves

What moves from Litify to Actionstep

Each row is a kind of record Litify holds, whether Actionstep has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping and three kinds are confirmed in the analysis.

Records in Litify and their place in Actionstep
RecordIn LitifyIn ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, with parties, calendar events, tasks, time and costs attached.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldParties, connected to intakes and matters through roles.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldHeld in Litify’s document component, with tags, versions and templates.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails appear on the case activity timeline. Mailboxes stay in the mail system.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeThe import tool has a file notes template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar events on the matter and the activity timeline.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks, including those generated by matter plans.Has a placeThe import tool has a tasks template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimekeeping, with time entries tied to the matter.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeldBilling and eBilling, aimed chiefly at insurance defence work.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 balancesTo be confirmedHas a placeTrust balances load per matter through the trust accounts import.Confirmed in the analysis
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 itselfHeldFields are added through Salesforce configuration.Has a placeData collections are built per matter type before values are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with conditional logic. Matter plans automate tasks.Has a placeRebuilt as Actionstep templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes with questionnaires, lead scoring and marketing source tracking.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 Litify.
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 Litify. 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 Litify 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 Litify is kept running until the checks on Actionstep are finished.

Where the data is now

A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.

  1. Parties and roles

    A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.

  2. Intakes become matters

    An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.

  3. Documents sit beside the records

    Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.

  4. Injury detail in related records

    Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.

  5. Automation stays behind

    Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.

More about moving off Litify

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.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Litify 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 Litify, 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 Litify: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Litify are frozen for an agreed window, the data is collected a final time and Actionstep goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Litify as at the cutover date. Litify 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 Litify 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 fromLitify
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 Litify 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

Litify to Actionstep: what firms ask

Do we need a Salesforce administrator to get our data out?

Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.

Are our documents included when Litify data is exported?

Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.

We are moving to Litify. Who does the configuration?

Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.

Do trust balances in Litify have a place in Actionstep?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Litify before the plan is fixed. If Actionstep turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Litify have a place in Actionstep?

Most of it does on paper. Notes, trust ledgers and 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 Litify data is loaded into Actionstep?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and 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

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

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