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

Data migration route

Amicus Attorney data to Microsoft SQL Server

Amicus Attorney is a server-based 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 Amicus Attorney holds and keeps it readable and open to queries.

FromAmicus AttorneyServer
  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. Trust money: Exported in full
  9. Intake: Exported in full
  10. Documents: Exported with mapping
  11. Emails: Exported with mapping
  12. Custom fields: Exported with mapping
  13. Templates: Exported with mapping
ToMicrosoft SQL ServerServer
  • 9 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amicus Attorney to Microsoft SQL Server

Each row is a kind of record Amicus Attorney holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route nine kinds of record carry across and four kinds need mapping.

Records in Amicus Attorney and their place in Microsoft SQL Server
RecordIn Amicus AttorneyIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled Files; contacts and firm members each have a role on a File.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldHas a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldAttached to Files; Amicus-managed documents use check-in and check-out.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 storeHeldEmails saved to Files; calendars and contacts sync with Exchange.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 notesHeldHas a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldCourt rule sets can be added for rules-based dates.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeld in partWith the Amicus Billing module; otherwise posted time goes to QuickBooks or PCLaw.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partTrust receipts, cheques and transfers come with Amicus Billing.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom fields, custom pages and Custom Records.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, plus Precedents that schedule a series of events.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partThe vendor lists lead management and intake; a File intake form is part of the product.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 Amicus Attorney.
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.

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 Attorney 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 Attorney 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 Attorney stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Amicus keeps its records in SQL Server on the firm’s own server, so the structure can be read directly once that server is reachable. The work is in the things particular to it: Files with a role for every person, custom pages and Custom Records, documents it manages itself, and money that may sit in Amicus Billing, in QuickBooks or in PCLaw depending on what the firm licensed.

  1. Matters are called Files

    A File holds its people, events, notes, time and documents, and each person has a role on it. Firm members have roles too, such as senior litigator or paralegal. Those roles map to the matter staff and party fields of the new system, and the mapping is agreed before anything is loaded.

  2. Custom pages and Custom Records

    Firms add their own fields through custom pages and can define whole record types called Custom Records. Some destinations take custom fields but have nothing like a custom record. The analysis shows each one with how often it is filled, and the firm decides which become fields, which become notes and which stay behind.

  3. Where the money sits

    With Amicus Billing, bills, receipts, retainers and trust activity are inside the database. Without it, posted time goes to QuickBooks or PCLaw and the ledgers are there. Either way the accounting link holds a map between Files and the customer, job or matter on the other side, and that map is used to match the two.

  4. Two databases and a folder

    The vendor’s own server move guide backs up two SQL databases, Amicus and Amicus Media, and copies the Amicus Attorney Server folder. All three are needed for a complete picture. Documents attached by reference sit wherever the user saved them, so links that no longer resolve are reported before the trial load.

  5. Precedents schedule events

    A Precedent in Amicus is a set of tasks and deadlines, assigned by role, that is applied to a File. It is closer to a workflow than to a document template. The events it has already created come across as calendar entries and tasks, and the Precedent itself is rebuilt in the destination’s workflow tool.

More about moving off Amicus Attorney

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

Amicus Attorney to Microsoft SQL Server: what firms ask

We are on an older Amicus version. Does that matter?

It changes where the data is. The Premium line runs on SQL Server, while the Small Firm Edition kept its data another way. Edition and version are confirmed at the start of the analysis, and the extraction is planned from that.

Do our time entries and unbilled work come across?

Posted and unposted time entries are both in the database with the File, firm member, activity code and rate. Unbilled time is loaded as unbilled so it can go on the next bill. Billed time is history: whether it loads as entries or stays in the read-only copy depends on the destination.

What happens to emails saved to Files?

Emails saved to a File are records in Amicus. They are filed to the same matter in the new system, as emails where it supports that and as documents where it does not. The Exchange link itself is not moved: mailboxes stay where they are in Microsoft 365 or on the firm’s mail server.

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

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 Attorney as at the export date.

Does everything in Amicus Attorney have a place in Microsoft SQL Server?

On paper, yes: each kind of record Amicus Attorney holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Amicus Attorney 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. 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

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

Moving from Amicus Attorney 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.