Data migration route
Amicus Accounting to Litify migration
Amicus Accounting is a desktop accounting and billing system, and Litify is a cloud case management system. Only part of what Amicus Accounting holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
Amicus AccountingDesktop- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Documents: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
LitifyCloud- 3 carried
- 1 mapped
- 6 to confirm
What moves
What moves from Amicus Accounting to Litify
Each row is a kind of record Amicus Accounting holds, whether Litify has a place for it, and what is planned. On this route three kinds of record carry across, one kind needs mapping and six 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 placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and vendors. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeLoaded to the document component and attached to matters. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | 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 entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldBills, pre-bills, receipts and reminder statements with or without interest. | Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldRegular and interest-bearing trust accounts, with transfers to pay invoices. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with audit trail, accounts payable and cheque writing. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom fields are created before loading. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Amicus Accounting.
- Carried with mapping
- Litify 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
Clients and jobs move. The books stay books.
An accounting or billing system and a case management system overlap less than firms expect. Amicus Accounting knows clients, jobs, time and invoices. Litify knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.
So the plan has two halves. Records with a place in Litify are loaded and checked there. The rest is exported from Amicus Accounting as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Amicus Accounting is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.
Amicus Accounting 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. Litify 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 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 Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Amicus Accounting and checking each trial against Amicus Accounting.
Analysis
We read what Amicus Accounting holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Accounting, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Litify as a trial and checked against Amicus Accounting: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Amicus Accounting are frozen for an agreed window, the data is collected a final time and Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Amicus Accounting as at the cutover date. Amicus Accounting 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 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 Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Amicus Accounting to Litify: 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.
Do trust balances in Amicus Accounting have a place in Litify?
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 Amicus Accounting before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Amicus Accounting have a place in Litify?
Most of it does on paper. Documents, notes, trust ledgers, the firm’s accounts, 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Amicus Accounting data is loaded into Litify?
Billing records are carried with mapping, so each mapping is agreed with you first. Documents, notes, trust ledgers, the firm’s accounts, custom fields and templates 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 Accounting and into Litify
Other destinations from Amicus Accounting
Other systems that move into Litify
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 Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Amicus Accounting to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.