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

Data migration route

Calendly to NetDocuments migration

Calendly is a cloud contacts and calendar tool, and NetDocuments 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.

FromCalendlyCloud
  1. Custom fields: Carried with mapping
  2. Templates: Carried with mapping
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 mapped
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Calendly to NetDocuments

Each row is a kind of record Calendly holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds need mapping and five kinds have no place in NetDocuments and are archived.

Records in Calendly and their place in NetDocuments
RecordIn CalendlyIn NetDocumentsWhat is planned
ContactsClients, other parties and referrersHeld in partA contacts list built from invitees, with custom fields. It exports to CSV.No placeKept as a readable archive
NotesFile notes, matter notes and contact notesHeld in partThe Notetaker feature produces meeting recaps where it is switched on.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldScheduled meetings with invitee details. The appointments also sit in the connected calendar.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partBooking payments taken through Stripe or PayPal are recorded against the meeting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partInvitee questions on each event type, and custom contact fields.Has a placeAs custom profile attributes, created in the repository before the load.Carried 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 partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partRouting forms and booking questions collect enquiry details before a meeting.No placeKept as a readable archive

What the plans mean

Carried with mapping
NetDocuments 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
NetDocuments 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.

NetDocuments 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 NetDocuments 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 NetDocuments 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 into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Calendly holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments 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

    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

Step 1 of 5: Start with the route

Moving fromCalendly
Moving toNetDocuments

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

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

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

NetDocuments 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 NetDocuments 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 NetDocuments?

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.

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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from Calendly to NetDocuments?

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

We reply within one business day.