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

Data migration route

iCalendar (.ics) files to Google Drive migration

iCalendar (.ics) files are contact and calendar data kept as files, and Google Drive is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromiCalendar (.ics) filesFiles
  1. Documents: Carried across
  2. Notes: Carried with mapping
ToGoogle DriveCloud
  1. Calendar: Kept as a readable archive
  2. Tasks: Kept as a readable archive
  3. Custom fields: Kept as a readable archive
Readable archiveNo place in Google Drive
  • 1 carried
  • 1 mapped
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iCalendar (.ics) files to Google Drive

Each row is a kind of record iCalendar (.ics) files hold, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and three kinds have no place in Google Drive and are archived.

Records in iCalendar (.ics) files and their place in Google Drive
RecordIn iCalendar (.ics) filesIn Google DriveWhat is planned
DocumentsFiles stored in or linked from the systemHeld in partThe format allows attachments by link or embedded; few exports include them.Has a placeAny file type, stored as uploaded or converted to Google formats.Carried across
NotesFile notes, matter notes and contact notesHeld in partEvent descriptions, and journal entries where the exporting program writes them.Has a place in partAs a Doc or Word file in the matter’s folder.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldEvents with start, end, summary, location, attendees, recurrence and alarms.No placeCalendar entries belong in Google Calendar.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partTo-do components, if the exporting program includes them.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partCategories, and non-standard properties some programs add.No placeKept as a readable archive

What the plans mean

Carried across
Google Drive has a place for this kind of record. It is loaded there and checked against iCalendar (.ics) files.
Carried with mapping
Google Drive 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
Google Drive has no place for it. It is exported in a format that opens without iCalendar (.ics) files 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.

Google Drive holds files, and most of what iCalendar (.ics) files hold 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 iCalendar (.ics) files, 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 Google Drive is limited before the export is copied in.

With iCalendar (.ics) files the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Google Drive.

Where the data is now

A calendar is the one part of a firm’s data where a mistake is noticed on the day it matters. Loading from .ics files is simple in outline and unforgiving in detail: a hearing an hour out, or a weekly meeting that repeats forever, damages trust in the new system quickly. The checks concentrate on future dates, recurring entries and time zones.

  1. An export is a snapshot

    The file holds the calendar as it stood at the moment of export. Appointments made the next morning are not in it. A trial export is used for testing, and the real one is taken inside the cutover freeze, after staff have stopped adding entries to the old calendar.

  2. Recurring entries are rules

    A fortnightly team meeting is one entry with a rule, plus exceptions for the weeks it was moved or cancelled. Programs differ in how they read those rules. A handful of real repeating appointments with known exceptions are checked date by date in the new calendar after the trial load.

  3. Time zones decide the hour

    Times may be written in UTC, against a named time zone defined in the file, or as floating times with no zone at all. A firm with offices in two states, or entries created while travelling, will have a mix. Future court dates are compared one for one against the old calendar.

  4. No link to the matter

    The format has no field for a matter. If the old system put the matter number in the summary or description, entries are linked by reading it. Otherwise they arrive on the right person’s calendar and unattached to any matter, and key dates are re-linked by hand for open matters.

  5. Identifiers stop double loading

    Every event carries a UID. The same meeting exported from five attendees’ calendars has one UID, so it can be loaded once and shown to all five. A second load after a failed first attempt updates entries by UID where the destination supports it, and does not duplicate them.

More about moving off iCalendar (.ics) files

Where it is going

Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.

  1. Shared drives, not My Drive

    Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.

  2. One drive cannot hold everything

    Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.

  3. Membership is the main control

    Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.

  4. The daily upload limit

    Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.

  5. Keep Office files as Office files

    Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.

More about moving into Google Drive

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what iCalendar (.ics) files hold and how it is organised, then agree with you where each kind of record will sit in Google Drive. 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 Google Drive and checked against iCalendar (.ics) files: 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 iCalendar (.ics) files, a final pass over a weekend picks up what changed since the trial. iCalendar (.ics) files are 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 iCalendar (.ics) files 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 fromiCalendar (.ics) files
Moving toGoogle Drive

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 iCalendar (.ics) files holds

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

Structure, permissions and handover

Google Drive is 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 Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.

What is agreed and set up

  • Shared drives by practice group, with a naming pattern
  • Managers and member access levels for each shared drive
  • External sharing rules set in the Admin console
  • Drive for desktop on PCs that need Explorer access
  • A standard subfolder set copied into every new matter
  • Transfer of leavers’ My Drive files as a standing procedure

Questions

iCalendar (.ics) files to Google Drive: what firms ask

Will our court dates and limitation reminders come across?

The dates will, as calendar entries. What may not survive is whatever made them special in the old system: a deadline type, a link to the matter, a rule that calculated the date. Reminders arrive as alarms on the entry where the export includes them. Every future critical date is listed and checked by the firm before go-live.

Do we need past appointments, or only future ones?

Either is workable. Past entries are evidence of attendances and are sometimes used to reconstruct time. A firm can bring a set number of years and keep the full export file with the fall-back records. Whatever is chosen, every future entry is in scope.

Our calendar is in Outlook. Is an .ics file the right way to move it?

Often not. Where the calendar lives in Microsoft 365 or Exchange and the firm is keeping that, the calendar does not need to move at all, and the new practice system connects to it. An .ics export is the fallback for calendars locked inside a product that offers no other way out.

Do documents from iCalendar (.ics) files keep their folders and dates in Google Drive?

Google Drive stores documents. Any file type, stored as uploaded or converted to Google formats. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

What happens to records Google Drive has no place for?

On this route that is calendar entries, tasks and custom fields. They are exported from iCalendar (.ics) files 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 iCalendar (.ics) files data is loaded into Google Drive?

Notes 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

iCalendar (.ics) files and Google Drive are the names and marks of their owners, used here only to identify the two systems.

Moving from iCalendar (.ics) files to Google Drive?

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

We reply within one business day.