Data migration route
Calendly to Actionstep migration
Calendly is a cloud contacts and calendar tool, and Actionstep is a cloud practice management system. This is a narrow move: the records Calendly holds are matched to the people and matters in Actionstep.
CalendlyCloud- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Billing: Confirmed in the analysis
ActionstepCloud- 4 carried
- 2 mapped
- 1 to confirm
What moves
What moves from Calendly to Actionstep
Each row is a kind of record Calendly holds, whether Actionstep has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | Held in partA contacts list built from invitees, with custom fields. It exports to CSV. | Has a placeImported first, then linked to matters through a parties import. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partThe Notetaker feature produces meeting recaps where it is switched on. | Has a placeThe import tool has a file notes template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldScheduled meetings with invitee details. The appointments also sit in the connected calendar. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partBooking payments taken through Stripe or PayPal are recorded against the meeting. | Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partInvitee questions on each event type, and custom contact fields. | Has a placeData collections are built per matter type before values are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partEvent types are reusable meeting set-ups with their own questions and rules. | Has a placeRebuilt as Actionstep templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partRouting forms and booking questions collect enquiry details before a meeting. | 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 Calendly.
- 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
A narrow move, checked like a large one.
A source like Calendly holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Actionstep, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.
The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Actionstep already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Calendly 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 Calendly is kept running until the checks on Actionstep are finished.
Where the data is now
Leaving Calendly
Calendly holds less than people expect. The appointments themselves already live in each lawyer’s own calendar, so what is left is the booking history, the invitees’ answers to the questions asked at booking, the contact list and the event types. A move means deciding which of those the new system should hold and rebuilding the booking pages there.
Meetings export as a spreadsheet
The meeting export is a CSV of whatever is filtered on the Calendar page. Each row carries the invitee’s name and contact details, the event type, the date and location, and any tracking codes or payment details. It is a record of bookings, not a calendar file, so it loads as a list of past consultations against a contact.
Answers given at booking
Most firms ask a question or two on the booking page: what the matter is about, who referred the client. Those answers are stored with the meeting. For a firm that used Calendly as its front door they are the intake record, and they are mapped to enquiry or matter fields in the destination.
Event types are rebuilt
An event type sets the kind of meeting, who hosts it and the questions asked of the invitee. Those settings are not part of the meeting export. Each one is written down and recreated in the new system’s booking tool, which is also the moment to retire the ones nobody books.
Links already in circulation
Booking links sit in email signatures, on the website and in old emails to clients. Clients go on clicking them long after the firm has moved. A list of where each link is published is made before cutover, and the website and signatures are changed on the day the new booking pages go live.
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.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Actionstep, they get a rehearsed cutover of their own.
Analysis
We read what Calendly 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 Calendly: 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
After a short freeze on changes in Calendly, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Calendly 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 Calendly 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 Calendly 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
Calendly to Actionstep: what firms ask
Do future bookings carry over?
Meetings already booked are in the lawyer’s own calendar, because that is where Calendly places them when the client books. The reschedule link in the client’s confirmation email should not be assumed to work once the Calendly account is closed, so upcoming bookings are listed before the account is closed and those clients are told how to change them.
Is it worth moving past appointments at all?
It depends on what else records them. If every consultation was also entered in the practice system, the booking history adds little. Where Calendly is the only place that shows who booked a first consultation and what they said about their matter, the export is loaded as notes or enquiries against each contact.
Do contacts from Calendly arrive in Actionstep without duplicates?
Actionstep has a place for contacts. Imported first, then linked to matters through a parties import. Duplicates are merged in Calendly before extraction where they can be identified, and the list is matched against contacts already in Actionstep. It is not always possible to find every one, so some may carry across.
Does everything in Calendly have a place in Actionstep?
Most of it does on paper. Billing records 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 Calendly data is loaded into Actionstep?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Billing records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Calendly and into Actionstep
Other destinations from Calendly
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.
Calendly and Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from Calendly 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.