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

Data migration route

AdvoLogix data to Microsoft SQL Server

AdvoLogix 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 AdvoLogix holds and keeps it readable and open to queries.

FromAdvoLogixCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: 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. Templates: Exported with mapping
  13. Trust money: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 8 carried
  • 4 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from AdvoLogix to Microsoft SQL Server

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

Records in AdvoLogix and their place in Microsoft SQL Server
RecordIn AdvoLogixIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters are the central record, with stage, status and a closed flag.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldSalesforce accounts and contacts, linked to matters as participants with roles.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldSalesforce files on the matter, or a linked NetDocuments, iManage, SharePoint or Google Drive store.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 partEmails sent from a matter are logged. Mailbox filing depends on an email integration.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 notesHeldComments recorded against the matter.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldA Matter Calendar, with date calculation rules.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldActivity plans and task checklists generate tasks on a matter.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime entries with timekeepers, rate groups and UTBMS codes. Expenses are tracked too.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeld in partTime, expenses and fees become billings, split between billing parties.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
Custom fieldsFields and record types the firm added itselfHeldCustom fields are added to matters and participants through Salesforce set-up.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldAdvoDoc document assembly templates. A HotDocs integration is also listed.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake records and intake forms, converted to matters.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 AdvoLogix.
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 AdvoLogix 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 AdvoLogix 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.

AdvoLogix 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 AdvoLogix will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

A move off AdvoLogix is a move out of a Salesforce org. The matter data is spread across the vendor’s packaged objects, standard Salesforce objects and whatever the firm’s administrator added over the years. An inventory of that org comes first: which objects hold live data, which fields are the firm’s own, and where the documents physically are.

  1. Participants carry the relationships

    A client, an opposing party or an expert is a Salesforce account or contact joined to the matter by a participant record with a role. Some participants are typed in as free text with no contact behind them. Both kinds are extracted, and the free-text ones are matched to real contacts or created as new ones before loading.

  2. Documents may sit elsewhere

    Files can be held as Salesforce files on the matter, or in NetDocuments, iManage, SharePoint or Google Drive through an integration. Many orgs have a mix, with older matters in one place and newer ones in another. Each matter is checked for where its files are before any document count is agreed.

  3. Billings are derived records

    Time and expense entries generate billing records, which can be split between billing parties and edited without changing the source entry. The two can therefore disagree by design. Which one is the record of truth for unbilled work is decided in the analysis, and totals are reconciled per matter against that choice.

  4. Every org is configured differently

    Matter stages, statuses, page layouts and automation are set by each firm’s Salesforce administrator. Two firms on the same product rarely share a field list. The mapping is written from the firm’s own org, including fields nobody remembers adding, and unused ones are listed for the firm to drop.

  5. Where the books are kept

    The help centre describes no ledger inside the matter application. An integration with Accounting Seed, a separate Salesforce application with its own objects, is offered for firms that keep their books on the platform. If the destination has built-in accounting, opening balances are taken from wherever the books were actually kept, not from the matter records.

More about moving off AdvoLogix

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 AdvoLogix holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything AdvoLogix 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 AdvoLogix: record counts, totals where AdvoLogix 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 AdvoLogix, the export is run a final time and checked again. There is nothing to go live. AdvoLogix 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 AdvoLogix 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 fromAdvoLogix
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 AdvoLogix 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

AdvoLogix to Microsoft SQL Server: what firms ask

Is AdvoLogix the same thing as Mitratech CaseCloud?

For practical purposes, yes. Mitratech introduced CaseCloud in November 2024 and describes it as built on Salesforce and AdvoLogix technologies. The help centre and many of the component names still say AdvoLogix. A firm that installed the product under the old name is holding the same kind of data in the same kind of org.

Do we lose our Salesforce history if we leave?

Salesforce keeps field history only where tracking was switched on, so what exists varies by org. Emails, tasks and events logged on a matter can be extracted with it. Field-level change history usually has no equivalent in a legal system, and it either comes across as a note or stays behind.

Can our time entries and rates come across?

Time entries, timekeepers and UTBMS codes are structured records with fields of their own. Rates are harder, because they are held in rate groups applied to matters and can be changed on a single matter. The analysis lists the rate that actually applied to each matter, so unbilled time is valued the same way after the move.

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

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 AdvoLogix before the plan is fixed.

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

Most of it does on paper. Trust ledgers 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 AdvoLogix is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Trust ledgers 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

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

Moving from AdvoLogix 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.