Data migration route
Amicus Attorney to SimpleLaw migration
Amicus Attorney is a server-based practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
Amicus AttorneyServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
SimpleLawCloud- 8 carried
- 4 mapped
- 1 to confirm
What moves
What moves from Amicus Attorney to SimpleLaw
Each row is a kind of record Amicus Attorney holds, whether SimpleLaw 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled Files; contacts and firm members each have a role on a File. | Has a place | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldAttached to Files; Amicus-managed documents use check-in and check-out. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails saved to Files; calendars and contacts sync with Exchange. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCourt rule sets can be added for rules-based dates. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partWith the Amicus Billing module; otherwise posted time goes to QuickBooks or PCLaw. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust receipts, cheques and transfers come with Amicus Billing. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields, custom pages and Custom Records. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, plus Precedents that schedule a series of events. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partThe vendor lists lead management and intake; a File intake form is part of the product. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Amicus Attorney.
- Carried with mapping
- SimpleLaw 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. Amicus Attorney and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Amicus Attorney’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Amicus Attorney runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SimpleLaw is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Amicus Attorney
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Amicus Attorney holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Amicus Attorney, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against Amicus Attorney: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Amicus Attorney are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Amicus Attorney 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 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
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 Attorney holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. 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
Setting up SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Amicus Attorney to SimpleLaw: 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.
Do trust balances in Amicus Attorney have a place in SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Amicus Attorney have a place in SimpleLaw?
Most of it does on paper. Emails 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Amicus Attorney data is loaded into SimpleLaw?
Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Amicus Attorney and into SimpleLaw
Other destinations from Amicus Attorney
Other systems that move into SimpleLaw
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 Attorney and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Amicus Attorney to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.