Data migration route
iCalendar (.ics) files to Centerbase migration
iCalendar (.ics) files are contact and calendar data kept as files, and Centerbase is a cloud practice management system. This is a narrow move: the records iCalendar (.ics) files hold are matched to the people and matters in Centerbase.
iCalendar (.ics) filesFiles- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Custom fields: Carried with mapping
CenterbaseCloud- 4 carried
- 1 mapped
What moves
What moves from iCalendar (.ics) files to Centerbase
Each row is a kind of record iCalendar (.ics) files hold, whether Centerbase has a place for it, and what is planned. On this route four kinds of record carry across and one kind needs mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | Held in partThe format allows attachments by link or embedded; few exports include them. | Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partEvent descriptions, and journal entries where the exporting program writes them. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldEvents with start, end, summary, location, attendees, recurrence and alarms. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTo-do components, if the exporting program includes them. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | Held in partCategories, and non-standard properties some programs add. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against iCalendar (.ics) files.
- Carried with mapping
- Centerbase 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
A narrow move, checked like a large one.
A source like iCalendar (.ics) files holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Centerbase, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.
The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Centerbase already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.
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 Centerbase.
Where the data is now
Leaving iCalendar (.ics) files
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Centerbase on this route, which makes it repeatable: a load can be run again until it is right.
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 Centerbase. 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 Centerbase 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.
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
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 iCalendar (.ics) files holds
What is in it, how its records link, and where each piece would sit in Centerbase. 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
iCalendar (.ics) files to Centerbase: 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 Centerbase?
Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. 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.
Does everything in iCalendar (.ics) files have a place in Centerbase?
On paper, yes: each kind of record iCalendar (.ics) files hold has a place in Centerbase. 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 Centerbase?
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.
Other routes
Other routes from iCalendar (.ics) files and into Centerbase
Other destinations from iCalendar (.ics) files
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.
iCalendar (.ics) files and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from iCalendar (.ics) files to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.