Data migration route
Calendly to iManage Cloud migration
Calendly is a cloud contacts and calendar tool, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
CalendlyCloud- Custom fields: Carried with mapping
- Templates: Carried with mapping
iManage CloudCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 mapped
- 5 archived
What moves
What moves from Calendly to iManage Cloud
Each row is a kind of record Calendly holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds need mapping and five kinds have no place in iManage Cloud 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 place | 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. | No placeFile notes can be loaded as documents on the matter. | Kept as a readable archive |
| 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. | No place | 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. | Has a place in partA fixed number of custom profile fields, each a validated list. | 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 place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | 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
- iManage Cloud 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
- iManage Cloud 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
Only the documents have a place here.
iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Calendly holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Calendly produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
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 iManage Cloud 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 iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 iManage Cloud. 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 iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
Calendly to iManage Cloud: 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 iManage Cloud without duplicates?
iManage Cloud has no place for contacts. The contact list from Calendly is exported as a spreadsheet and kept as a readable archive.
What happens to records iManage Cloud has no place for?
On this route that is contacts, notes, calendar entries, billing records 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 iManage Cloud?
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 Calendly and into iManage Cloud
Other destinations from Calendly
Other systems that move into iManage Cloud
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 iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Calendly to iManage Cloud?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.