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

Data migration route

Curo365 to Server drives migration

Curo365 is a cloud practice management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromCuro365Cloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Confirmed in the analysis
  4. Trust money: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Firm accounts: Kept as a readable archive
  8. Custom fields: Kept as a readable archive
  9. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 1 mapped
  • 3 to confirm
  • 9 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Curo365 to Server drives

Each row is a kind of record Curo365 holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, nine kinds have no place in Server drives and are archived and three kinds are confirmed in the analysis.

Records in Curo365 and their place in Server drives
RecordIn Curo365In Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldNo placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldClient records and relationships are held in Dynamics 365.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldManaged in SharePoint.Has a placeFiles in folders, named and dated during the load.Carried across
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 .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars are Exchange and Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partAutomated workflows for firm processes; task records were not confirmed.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime can be entered from Outlook.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling and invoicing are part of the product.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeOnly as exported ledger reports kept as files.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partKept in Microsoft Business Central or QuickBooks, not inside Curo365 itself.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldBuilt on Dynamics 365, where a firm can add its own fields.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as Word files; merge fields tied to the old system stop working.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient management and marketing use Dynamics 365 CRM functions.No placeKept as a readable archive

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against Curo365.
Carried with mapping
Server drives 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
Server drives 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 Server drives 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 Server drives do 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.

Curo365 is hosted by its maker and Server drives sit 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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Curo365 holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Server drives 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.

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

Step 1 of 5: Start with the route

Moving fromCuro365
Moving toServer drives

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 Server drives. 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

Server drives are 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 server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Curo365 to Server drives: 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 Server drives?

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 Server drives 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 Server drives have no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, the firm’s accounts, custom fields 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 Server drives?

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

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 Server drives are the names and marks of their owners, used here only to identify the two systems.

Moving from Curo365 to Server drives?

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

We reply within one business day.