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

Data migration route

Calendly to SimpleLaw migration

Calendly is a cloud contacts and calendar tool, and SimpleLaw is a cloud practice management system. This is a narrow move: the records Calendly holds are matched to the people and matters in SimpleLaw.

FromCalendlyCloud
  1. Contacts: Carried across
  2. Notes: Carried across
  3. Calendar: Carried across
  4. Intake: Carried across
  5. Custom fields: Carried with mapping
  6. Templates: Carried with mapping
  7. Billing: Confirmed in the analysis
ToSimpleLawCloud
  • 4 carried
  • 2 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Calendly to SimpleLaw

Each row is a kind of record Calendly holds, whether SimpleLaw 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.

Records in Calendly and their place in SimpleLaw
RecordIn CalendlyIn SimpleLawWhat is planned
ContactsClients, other parties and referrersHeld in partA contacts list built from invitees, with custom fields. It exports to CSV.Has a placeAs leads, clients or other contacts in the CRM.Carried across
NotesFile notes, matter notes and contact notesHeld in partThe Notetaker feature produces meeting recaps where it is switched on.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldScheduled meetings with invitee details. The appointments also sit in the connected calendar.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partBooking payments taken through Stripe or PayPal are recorded against the meeting.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partInvitee questions on each event type, and custom contact fields.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeld in partEvent types are reusable meeting set-ups with their own questions and rules.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partRouting forms and booking questions collect enquiry details before a meeting.Has a placeLeads and intake forms.Carried across

What the plans mean

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

Where the data is now

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.

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

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

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

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

More about moving off Calendly

Where it is going

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

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 SimpleLaw, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Calendly holds and how it is organised, then agree with you where each kind of record will sit in SimpleLaw. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into SimpleLaw 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.

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

Step 1 of 5: Start with the route

Moving fromCalendly
Moving toSimpleLaw

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

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Calendly to SimpleLaw: 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 SimpleLaw without duplicates?

SimpleLaw has a place for contacts. As leads, clients or other contacts in the CRM. Duplicates are merged in Calendly before extraction where they can be identified, and the list is matched against contacts already in SimpleLaw. It is not always possible to find every one, so some may carry across.

Does everything in Calendly have a place in SimpleLaw?

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

What has to be decided before Calendly data is loaded into SimpleLaw?

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.

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

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

Moving from Calendly to SimpleLaw?

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

We reply within one business day.