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

Data migration route

Curo365 data to Microsoft SQL Server

Curo365 is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Curo365 holds and keeps it readable and open to queries.

FromCuro365Cloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Firm accounts: Exported in full
  8. Intake: Exported in full
  9. Documents: Exported with mapping
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Templates: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 8 carried
  • 3 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Curo365 to Microsoft SQL Server

Each row is a kind of record Curo365 holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping and three kinds are confirmed in the analysis.

Records in Curo365 and their place in Microsoft SQL Server
RecordIn Curo365In Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldClient records and relationships are held in Dynamics 365.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldManaged in SharePoint.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeld in partMail stays in Exchange and Outlook; what is filed to a matter was not confirmed.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars are Exchange and Outlook.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partAutomated workflows for firm processes; task records were not confirmed.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime can be entered from Outlook.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBilling and invoicing are part of the product.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTransactions and balances for look-up; it is not a trust accounting system.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partKept in Microsoft Business Central or QuickBooks, not inside Curo365 itself.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldBuilt on Dynamics 365, where a firm can add its own fields.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedent files can be stored; automation does not run here.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient management and marketing use Dynamics 365 CRM functions.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Curo365.
Exported with mapping
Microsoft SQL Server 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.

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

Not a new system. A complete copy the firm can query.

Writing Curo365 out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Curo365 as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Curo365 is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Curo365 will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

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.

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

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

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

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

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

More about moving off Curo365

Where it is going

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Curo365 holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Curo365 holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Curo365: record counts, totals where Curo365 holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Curo365, the export is run a final time and checked again. There is nothing to go live. Curo365 is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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

Step 1 of 5: Start with the route

Moving fromCuro365
Moving toMicrosoft SQL Server

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 Curo365 holds

    What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Curo365 to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from Curo365?

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.

Does everything in Curo365 have a place in Microsoft SQL Server?

Most of it does on paper. Notes, trust ledgers and templates 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Curo365 is written out to Microsoft SQL Server?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. Notes, trust ledgers and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Curo365 and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Curo365 to Microsoft SQL Server?

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

We reply within one business day.