Data migration route
iCalendar (.ics) files to SurePoint Finance Enterprise migration
iCalendar (.ics) files are contact and calendar data kept as files, and SurePoint Finance Enterprise 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 SurePoint Finance Enterprise.
iCalendar (.ics) filesFiles- Calendar: Carried across
- Documents: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SurePoint Finance EnterpriseCloud- 1 carried
- 4 to confirm
What moves
What moves from iCalendar (.ics) files to SurePoint Finance Enterprise
Each row is a kind of record iCalendar (.ics) files hold, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route one kind of record carries across and four kinds are confirmed in the analysis.
| 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. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partEvent descriptions, and journal entries where the exporting program writes them. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldEvents with start, end, summary, location, attendees, recurrence and alarms. | Has a placeCalendar entries and dockets. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTo-do components, if the exporting program includes them. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partCategories, and non-standard properties some programs add. | To be confirmed | Confirmed in the analysis |
What the plans mean
- Carried across
- SurePoint Finance Enterprise has a place for this kind of record. It is loaded there and checked against iCalendar (.ics) files.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
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 SurePoint Finance Enterprise, 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise.
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 SurePoint Finance Enterprise
Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.
Entities and tax IDs first
The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.
History has to balance
Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.
E-billing detail on time entries
For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.
Dockets as well as appointments
Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.
Cost recovery codes
Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SurePoint Finance Enterprise 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise
Loaded data is not yet a working system. This is what NewLaw sets up in SurePoint Finance Enterprise, beyond the migration, so that people can work in it from the first day.
The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.
Set-up decisions in SurePoint Finance Enterprise
- Entity structure, tax IDs and the chart of accounts
- Bank and trust accounts with reconciliation set-up
- Timekeeper rates, classifications and task code sets
- Pre-bill approval steps and client billing rules
- LEDES e-billing formats for each corporate client
- Management and compensation reports the partners use
Questions
iCalendar (.ics) files to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in iCalendar (.ics) files before the plan is fixed. Documents that have no place in SurePoint Finance Enterprise are exported into folders by client and matter.
Does everything in iCalendar (.ics) files have a place in SurePoint Finance Enterprise?
Most of it does on paper. Documents, notes, tasks and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.
What has to be decided before iCalendar (.ics) files data is loaded into SurePoint Finance Enterprise?
Documents, notes, tasks and custom fields are confirmed in the analysis. 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 SurePoint Finance Enterprise
Other destinations from iCalendar (.ics) files
Other systems that move into SurePoint Finance Enterprise
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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.
Moving from iCalendar (.ics) files to SurePoint Finance Enterprise?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.