Data migration route
Curo365 to SharePoint migration
Curo365 is a cloud practice management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
Curo365Cloud- Documents: Carried across
- Matters: Carried with mapping
- Contacts: Carried with mapping
- Emails: Carried with mapping
- Calendar: Carried with mapping
- Tasks: Carried with mapping
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Templates: Confirmed in the analysis
SharePointCloud- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 6 mapped
- 3 to confirm
- 4 archived
What moves
What moves from Curo365 to SharePoint
Each row is a kind of record Curo365 holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, six kinds need mapping, four kinds have no place in SharePoint and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldClient records and relationships are held in Dynamics 365. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldManaged in SharePoint. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partMail stays in Exchange and Outlook; what is filed to a matter was not confirmed. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as rows in a notes list if one is built. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalendars are Exchange and Outlook. | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | Held in partAutomated workflows for firm processes; task records were not confirmed. | Has a place in partPossible as a list; no legal workflow built in. | Carried with mapping |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime can be entered from Outlook. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBilling and invoicing are part of the product. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partKept in Microsoft Business Central or QuickBooks, not inside Curo365 itself. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldBuilt on Dynamics 365, where a firm can add its own fields. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as files; templates can be offered from a library. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partClient management and marketing use Dynamics 365 CRM functions. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against Curo365.
- Carried with mapping
- SharePoint holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- 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.
- Kept as a readable archive
- SharePoint has no place for it. It is exported in a format that opens without Curo365 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Curo365 into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Curo365.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Curo365 depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Curo365 is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving Curo365
Curo365 is one product on the screen and several Microsoft services underneath. Matters are in Dynamics 365, documents in SharePoint, email and diaries in Exchange, the ledger in Business Central or QuickBooks. Leaving it means collecting from each of those and putting the links back together. The documents and mail are in the firm’s own Microsoft 365, which changes what has to move at all.
Four places, one matter
A single matter has its details in Dynamics 365, its files in SharePoint, its emails and appointments in Outlook and its money in the accounting package. Each is extracted separately and joined on the matter number. The first trial load is mainly a test of that join: does every document folder find its matter.
Documents may not need moving
The files are in SharePoint in the firm’s Microsoft 365. If the new system can work with SharePoint, they can stay where they are and be linked. If it has its own document store, they are copied in with their folder structure and dates. That choice is the largest single factor in the size of the job.
The ledger is beside it
Accounting is done in Microsoft Business Central or in QuickBooks, so the general ledger and payables are taken from that package and not from Curo365. Billing history and the debtor ledger are compared before cutover so that both agree on what each client owes. Where client money is recorded is confirmed in the analysis.
Calendars belong to mailboxes
Appointments are ordinary Outlook items in each person’s mailbox, and they remain there after the move. What can be lost is the link from an appointment to its matter. Court dates and limitation dates are identified and loaded into the new system’s own calendar, so they do not depend on one lawyer’s mailbox.
Power BI reports
Partners often run the firm from Power BI dashboards that read Curo365 data. A dashboard is not a record and cannot be migrated. The reports people open each week are listed, with the figures each one shows, and rebuilt against the new system or replaced by its own reporting.
Where it is going
Arriving in SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Curo365 holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against Curo365: 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 Curo365, a final pass over a weekend picks up what changed since the trial. Curo365 is 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 Curo365 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 Curo365 holds
What is in it, how its records link, and where each piece would sit in SharePoint. 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
SharePoint 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
Curo365 to SharePoint: what firms ask
Our documents are already in SharePoint. Do we have to move them?
Not always. They are in the firm’s own Microsoft 365 and remain there whatever happens to the practice system. If the destination can link to SharePoint, the folders are re-attached to the new matters. If it stores documents itself, they are copied across and the SharePoint library is kept read only for a period.
We have customised Curo365 heavily. Does that complicate a move?
It adds work, and the work is predictable. Dynamics 365 lets a firm add fields, tables and workflows, and those additions are visible in the configuration. The analysis lists each one with how many records use it. Fields with real data are mapped. Workflows are described in plain words so they can be rebuilt or dropped.
Will entering time from Outlook still work?
The entries already made are in Curo365 and move as time records, billed and unbilled. Entering time from Outlook afterwards depends on whether the new system has an Outlook add-in of its own. That is confirmed for the chosen destination in the analysis, and fee earners are shown the new method before go-live.
Do trust balances in Curo365 have a place in SharePoint?
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 Curo365 before the plan is fixed. If SharePoint turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records SharePoint has no place for?
On this route that is time entries, billing records, the firm’s accounts and intake records. They are exported from Curo365 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 Curo365 data is loaded into SharePoint?
Matters, contacts, emails, calendar entries, tasks and custom fields are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and templates 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 Curo365 and into SharePoint
Other destinations from Curo365
Other systems that move into SharePoint
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.
Curo365 and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Curo365 to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.