Data migration route
Juris to Actionstep migration
Juris is a server-based accounting and billing system, and Actionstep is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Actionstep are built around them.
- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Billing: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
ActionstepCloud- 7 carried
- 1 mapped
- 5 to confirm
What moves
What moves from Juris to Actionstep
Each row is a kind of record Juris holds, whether Actionstep has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping and five kinds are confirmed in the analysis.
| Record | In Juris | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as financial records, coded by lawyer, practice class and office. | Has a placeImported with a matter type, a status and the old number as File Reference. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients, vendors and names typed on note cards. | Has a placeImported first, then linked to matters through a parties import. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeFiled in matter folders; not part of the spreadsheet import tool. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeSaved emails sit on the matter they were filed to. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNote cards at client or matter level. | Has a placeThe import tool has a file notes template. | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partThe vendor’s site lists a Juris Calendar beside the main product. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeThe import tool has a tasks template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered in Juris, Juris Suite or the Juris Go mobile app. | Has a placeTime entries and disbursements each have an import template. | Carried across |
| BillingInvoices, payments and debtor balances | HeldIncludes electronic billing. | 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 balances | Held | Has a placeTrust balances load per matter through the trust accounts import. | Carried across |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with multi-level sub-accounts, payables and cheque reconciliation. | Has a placeOpening balances are entered against the general ledger, or the books stay in Xero. | Carried across |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeData collections are built per matter type before values are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a placeRebuilt as Actionstep templates with its merge fields. | Confirmed in the analysis |
What the plans mean
- Carried across
- Actionstep has a place for this kind of record. It is loaded there and checked against Juris.
- 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Juris needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Juris. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Actionstep are agreed to the trial balance and aged debtors from Juris as at the cutover date, and that load is rehearsed before it is done for real.
Juris runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Actionstep is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Juris
Juris holds the firm’s financial history and little else, so a move off it is mostly about money and the codes that classify it. Work in progress, receivables, trust, payables and the ledger are each agreed to a Juris report. Matter documents and calendars usually live in another product beside it, and that product is brought into the same plan.
Three kinds of charge
Juris separates fees, cash expenses and non-cash expenses, and supports accrual, billed and cash accounting methods. Many destinations know only time and disbursements. The mapping has to say where non-cash expenses go, or unbilled and billed cost totals will not agree after the load.
Codes carry the reporting
Billing lawyer, originating lawyer, working timekeeper, practice class, office and billing agreement are all coded on the matter. Partner reports are built on them. Each code table is extracted and mapped, and codes that have drifted into near-duplicates are tidied in Juris before extraction.
Note cards feed conflict searches
Clients and matters can have note cards with other names and special information, and the conflict search reads them. They are where related parties were typed when there was no better field. Note cards come across as notes, and names inside them are flagged in case the firm wants them as contacts.
Juris Suite is a second layer
Firms with Juris Suite enter time, run collections and keep budgets through it. Budgets and collection notes are extra records worth asking about. They are listed in the analysis so nobody finds after go-live that the collections history was never in scope.
Sub-accounts in the chart
The chart of accounts can be split into multi-level sub-accounts to match how the firm is organised. A destination with a flat chart needs those collapsed or turned into tracking categories. The firm’s accountant agrees the new chart first, and the closing trial balance is restated into it before loading.
Where it is going
Arriving in Actionstep
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Juris 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.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Juris, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Actionstep as a trial and checked against Juris: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Juris 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. Juris 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 Juris 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Juris 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.
- 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
Juris to Actionstep: what firms ask
Can we keep our client and matter codes?
Juris codes are carried over wherever the destination allows a firm-set number, with the same padding and separators so old bills still match. If the new system numbers matters itself, the Juris code is stored as a reference and printed on invoices where clients expect to see it.
How much billing history should we bring?
Enough to answer a client’s question about a bill and to run aged debtors properly. Open invoices are loaded with their original dates. Paid invoices from earlier years can be loaded as summaries or left in Juris, kept read only. The destination’s limits usually decide it.
Our e-billing clients have strict formats. What happens?
The task codes, timekeeper classifications and client rates behind your e-bills are extracted and rebuilt in the new system. Past submissions stay where they are. Before go-live one real invoice for each e-billing client is produced from the trial load and checked against that client’s rules.
Do trust balances in Juris 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 Juris 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 Juris have a place in Actionstep?
Most of it does on paper. Documents, emails, tasks, custom fields and templates 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 Juris data is loaded into Actionstep?
Billing records are carried with mapping, so each mapping is agreed with you first. Documents, emails, tasks, custom fields and templates are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Juris and into Actionstep
Other destinations from Juris
Other systems that move into Actionstep
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Juris and Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from Juris 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.