Data migration route
Calendly to Server drives migration
Calendly is a cloud contacts and calendar tool, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.
CalendlyCloud- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Billing: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 mapped
- 5 archived
What moves
What moves from Calendly to Server drives
Each row is a kind of record Calendly holds, whether Server drives have a place for it, and what is planned. On this route two kinds need mapping and five kinds have no place in Server drives and are archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | Held in partA contacts list built from invitees, with custom fields. It exports to CSV. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| NotesFile notes, matter notes and contact notes | Held in partThe Notetaker feature produces meeting recaps where it is switched on. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldScheduled meetings with invitee details. The appointments also sit in the connected calendar. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partBooking payments taken through Stripe or PayPal are recorded against the meeting. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partInvitee questions on each event type, and custom contact fields. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partEvent types are reusable meeting set-ups with their own questions and rules. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partRouting forms and booking questions collect enquiry details before a meeting. | No place | Kept as a readable archive |
What the plans mean
- Carried with mapping
- Server drives holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without Calendly and handed to the firm as a read-only archive.
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
An export the firm can open without the system.
Server drives hold files, and most of what Calendly holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Calendly, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.
Calendly is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Calendly will release depends on its export tools, and that is confirmed in the analysis.
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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Calendly holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives 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
There is no financial cutover on this route. After a short freeze on changes in Calendly, a final pass over a weekend picks up what changed since the trial. 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 Server drives. 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
Structure, permissions and handover
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
Calendly to Server drives: 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 Server drives without duplicates?
Server drives have no place for contacts. Can be kept only as an exported spreadsheet. The contact list from Calendly is exported as a spreadsheet and kept as a readable archive.
What happens to records Server drives have no place for?
On this route that is contacts, calendar entries, billing records, custom fields and intake records. They are exported from Calendly in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Calendly data is loaded into Server drives?
Notes 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 Calendly and into Server drives
Other destinations from Calendly
Other systems that move into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Calendly to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.