Data migration route
Amicus Accounting data to Microsoft SQL Server
Amicus Accounting is a desktop accounting and billing 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 Amicus Accounting holds and keeps it readable and open to queries.
Amicus AccountingDesktop- Matters: Exported in full
- Contacts: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Documents: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
Microsoft SQL ServerServer- 6 carried
- 4 to confirm
What moves
What moves from Amicus Accounting to Microsoft SQL Server
Each row is a kind of record Amicus Accounting holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route six kinds of record carry across and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient Files, each with a Client/Matter ID, file type and responsible lawyer. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | Held in partClients and vendors. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldHourly and flat-fee entries, including those posted from Amicus Attorney. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldBills, pre-bills, receipts and reminder statements with or without interest. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldRegular and interest-bearing trust accounts, with transfers to pay invoices. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with audit trail, accounts payable and cheque writing. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs added columns, or a table of field names and values. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedent files can be stored; automation does not run here. | Confirmed in the analysis |
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 Amicus Accounting.
- 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 Amicus Accounting 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 Amicus Accounting 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.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Amicus Accounting stays untouched until the copy in Microsoft SQL Server has been checked.
Where the data is now
Leaving Amicus Accounting
The books here are self-contained: one folder of data files holds billing, trust and the general ledger. Trust balances, unpaid bills, unbilled time and expenses and ledger balances are taken at a month end and agreed to the program’s own reports. Client files are then matched to the matters held in Amicus Attorney, or wherever else the firm keeps its files.
The ID holds two numbers
A Client/Matter ID is one number in which the leading digits are the client and the last three are the matter. Gavel & Gown suggested restarting the client sequence each year, so 120001 can mean the first client of 2012. The ID is split on load, and the year convention is kept only if the firm still wants it.
Data files in the program folder
The data is a set of DBF, FPT and CDX files, with DBC database files, in the folder where the program was installed. Those are exactly what the built-in backup copies. A copy of that folder, taken with everyone logged out, holds the whole set of books as they stood at that moment.
Closed files keep two extras
Closing a file asks for a closed number and a destruction date, and a second step moves its transactions to the closed file. Neither field exists in most systems. The closed number is often what is written on the archive box, so it is carried as a reference on the closed matter.
Two kinds of trust account
Trust can be held in a regular account or in an interest-bearing one. Both are loaded as trust ledgers, but against different bank accounts. The trial load is checked to the trust listing for each bank account, not just to a firm-wide total.
Where it is going
Arriving in Microsoft SQL Server
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Amicus Accounting holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Amicus Accounting holds is in scope unless you take it out.
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.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Amicus Accounting: record counts, totals where Amicus Accounting holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Amicus Accounting, the export is run a final time and checked again. There is nothing to go live. Amicus Accounting 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 Amicus Accounting 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 Amicus Accounting 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.
- 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
Amicus Accounting to Microsoft SQL Server: what firms ask
Is Amicus Accounting still sold?
It is not on CARET’s current product list, which offers billing inside Amicus Attorney. The most recent vendor pages describing it that could be found date from 2011 to 2013. Treat support and licensing as something to confirm with CARET directly. None of that changes how the data is read.
Can the general ledger history come across?
Balances can, as an opening journal at an agreed date. Posted history depends on the destination: practice systems that rely on Xero or QuickBooks for the ledger have nowhere to put it. Prior years then stay in the old program, kept read only, and in printed year-end reports.
We also use Amicus Attorney. Which one is the master list?
Money follows the accounting program; people, dates and documents follow Amicus Attorney. The link between them paired Files with Client/Matter IDs, and that pairing is rebuilt and checked during the analysis. Files that exist on one side only are listed, since each is either a matter never billed or a duplicate.
Does the copy in Microsoft SQL Server hold trust ledgers from Amicus Accounting?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Amicus Accounting as at the export date.
Does everything in Amicus Accounting have a place in Microsoft SQL Server?
Most of it does on paper. Documents, notes, custom fields 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 Amicus Accounting is written out to Microsoft SQL Server?
Documents, notes, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Amicus Accounting and into Microsoft SQL Server
Other destinations from Amicus Accounting
Other systems that move into Microsoft SQL Server
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.
Amicus Accounting and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Amicus Accounting 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.