Data migration route
iCalendar (.ics) files to Sync.com migration
iCalendar (.ics) files are contact and calendar data kept as files, and Sync.com is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
iCalendar (.ics) filesFiles- Documents: Carried across
- Notes: Carried with mapping
Sync.comCloud- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 1 mapped
- 3 archived
What moves
What moves from iCalendar (.ics) files to Sync.com
Each row is a kind of record iCalendar (.ics) files hold, whether Sync.com 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 Sync.com and are archived.
| 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 placeFiles and folders within the path limit; some file types are skipped by the apps. | 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 in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldEvents with start, end, summary, location, attendees, recurrence and alarms. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partTo-do components, if the exporting program includes them. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partCategories, and non-standard properties some programs add. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against iCalendar (.ics) files.
- Carried with mapping
- Sync.com 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
- Sync.com 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.
Sync.com 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 Sync.com 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 Sync.com.
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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com 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 Sync.com. 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 Sync.com 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 Sync.com. 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
Structure, permissions and handover
Sync.com 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 Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
iCalendar (.ics) files to Sync.com: 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 Sync.com?
Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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 Sync.com 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 Sync.com?
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.
Other routes
Other routes from iCalendar (.ics) files and into Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from iCalendar (.ics) files to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.