Data migration route
Act! to Actionstep migration
Act! is a desktop CRM and intake system, and Actionstep is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Actionstep.
Act!Desktop- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
ActionstepCloud- 7 carried
- 2 mapped
What moves
What moves from Act! to Actionstep
Each row is a kind of record Act! holds, whether Actionstep has a place for it, and what is planned. On this route seven kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldContacts, secondary contacts, companies and groups. | Has a placeImported first, then linked to matters through a parties import. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partFiles attached to records are kept in an attachments folder beside the database. | Has a placeFiled in matter folders; not part of the spreadsheet import tool. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails can be recorded in a contact’s history through the Outlook or Gmail link. | Has a placeSaved emails sit on the matter they were filed to. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes and history entries are kept against each contact. | Has a placeThe import tool has a file notes template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldActivities: calls, meetings and to-dos with dates. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTo-dos are one kind of activity. | Has a placeThe import tool has a tasks template. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldFields are added through Define Fields and placed on screen layouts. | Has a placeData collections are built per matter type before values are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, report templates and layouts are stored with the database. | Has a placeRebuilt as Actionstep templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partOpportunities move through a sales pipeline; web forms come with the marketing tools. | Has a place | Carried across |
What the plans mean
- Carried across
- Actionstep has a place for this kind of record. It is loaded there and checked against Act!.
- 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.
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
Contacts and enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Act! to Actionstep is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because Actionstep will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever Actionstep or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
Act! 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 Act!
A move off Act! starts with finding the database. Many firms have more than one: a main copy on a server and remote copies that synchronise from laptops. Once the working copy is identified, contacts, companies, groups, notes, history and activities are read from it and matched to the people and matters in the new system. Attached files come from a separate folder.
The database and its attachments
The desktop edition’s own backup produces a zip file holding the database, attached documents, layouts, document templates, report templates and saved queries. Attachments can be left out of that backup, so a copy made for another purpose may not include them. The extraction is taken from a backup known to include the attachments folder.
Remote copies that synchronise
Act! lets a laptop carry a remote database that synchronises with the main one. A remote copy that has not synchronised for months holds notes and history nobody else has seen. Before extraction each remote user synchronises a final time, and the main database is treated as the single source.
History is the valuable part
A plain contact export gives names and addresses. What a firm usually wants to keep is the history: years of calls, meetings and correspondence against each person. History, notes and activities are separate record types linked to contacts, and each one needs a decided home in the destination, usually as dated notes on the client or the matter.
Groups and companies
Groups are how many Act! users sort their contacts: a Christmas card list, a referrer list, clients of one partner. A contact can sit in several groups and can be linked to a company record. Those memberships become tags, categories or mailing lists in the new system, and the mapping is agreed group by group.
Fields the firm defined
Act! databases are often customised over many years, with fields added through Define Fields and laid out on custom screens. Some are still in use and some were abandoned long ago. Each defined field is listed with a count of the records that use it, so the firm can choose which ones are worth carrying.
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.
Nothing financial lands in Actionstep on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Act! holds and how it is organised, then agree with you where each kind of record will sit in Actionstep. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Actionstep and checked against Act!: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Act!, a final pass over a weekend picks up what changed since the trial. Act! 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 Act! 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 Act! 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
Act! to Actionstep: what firms ask
Can the history against each contact come across?
Usually, as dated notes. History entries, notes and activities are held separately from the contact’s own fields, so they are extracted as their own lists and linked back to the right person. Whether they land on the contact or on a matter depends on how the destination files notes, and that is settled in the analysis.
We have several Act! databases. Which one is moved?
All of them can be read, but they are combined before loading, not after. Act! checks for duplicates on fields the administrator chooses, so two databases may hold the same person under slightly different details. The databases are compared, the overlaps are listed, and the firm decides which record wins.
What happens to documents attached to contacts?
Attached files live in a folder beside the database, with the link held on the contact’s record. They are copied out with those links intact and filed against the matching client or matter in the new system. A file attached to a contact who has several matters needs a rule for where it goes.
Do documents from Act! keep their folders and dates in Actionstep?
Actionstep stores documents. Filed in matter folders; not part of the spreadsheet import tool. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Act! have a place in Actionstep?
On paper, yes: each kind of record Act! holds has a place in Actionstep. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Act! data is loaded into Actionstep?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Act! and 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.
Act! and Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from Act! 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.