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

Data migration route

iCalendar (.ics) files to Lawmatics migration

iCalendar (.ics) files are contact and calendar data kept as files, and Lawmatics is a cloud CRM and intake system. The records move, and the pipeline, forms and automations are set up again in Lawmatics.

FromiCalendar (.ics) filesFiles
  1. Notes: Carried across
  2. Calendar: Carried across
  3. Tasks: Carried across
  4. Documents: Carried with mapping
  5. Custom fields: Carried with mapping
ToLawmaticsCloud
  • 3 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iCalendar (.ics) files to Lawmatics

Each row is a kind of record iCalendar (.ics) files hold, whether Lawmatics has a place for it, and what is planned. On this route three kinds of record carry across and two kinds need mapping.

Records in iCalendar (.ics) files and their place in Lawmatics
RecordIn iCalendar (.ics) filesIn LawmaticsWhat 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 place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partEvent descriptions, and journal entries where the exporting program writes them.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents with start, end, summary, location, attendees, recurrence and alarms.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partTo-do components, if the exporting program includes them.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeld in partCategories, and non-standard properties some programs add.Has a placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against iCalendar (.ics) files.
Carried with mapping
Lawmatics holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Contacts and leads move. Forms and automations are rebuilt.

Between two tools that manage contacts and enquiries, the records move cleanly and the machinery does not. Each pipeline stage in iCalendar (.ics) files needs an equivalent in Lawmatics, and stage names seldom line up. Open leads are loaded at the matching stage so that follow-up carries on. Closed and lost leads come across with their outcome, because conversion reporting depends on them. Sources and referrers are put into one list first.

Forms, email templates, sequences and automations are rebuilt by hand. It is worth doing on purpose: most firms find a sequence still running that nobody remembers setting up. Web forms and booking links on the firm’s site are repointed at cutover, and a test enquiry is put through each one. Consent and unsubscribe records move with the contacts and are checked separately, since a mistake there means emailing people who opted out.

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

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Lawmatics 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 Lawmatics. 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 Lawmatics 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 toLawmatics

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

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

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

iCalendar (.ics) files to Lawmatics: 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 Lawmatics?

In part. Files and folders on each matter, added by upload or API, not by the spreadsheet import. The structure in iCalendar (.ics) files is mapped to what Lawmatics offers and you see the mapping before the load. File dates are carried.

Does everything in iCalendar (.ics) files have a place in Lawmatics?

On paper, yes: each kind of record iCalendar (.ics) files hold has a place in Lawmatics. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before iCalendar (.ics) files data is loaded into Lawmatics?

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

Moving from iCalendar (.ics) files to Lawmatics?

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

We reply within one business day.