Data migration route
Amicus Cloud to Filevine migration
Amicus Cloud is a cloud practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Amicus CloudCloud- Matters: Carried across
- Contacts: Carried across
- Emails: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- 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
- Intake: Confirmed in the analysis
FilevineCloud- 5 carried
- 2 mapped
- 7 to confirm
What moves
What moves from Amicus Cloud to Filevine
Each row is a kind of record Amicus Cloud holds, whether Filevine has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping and seven kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldThe vendor lists matter management as a core feature. | Has a placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeDocs section with folders. Templated project folders can be set per type. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | Held in partEmail is one of the main modules; how messages are tied to matters is not documented publicly. | Has a placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held | Has a placeDeadlines and calendar events. | 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 in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldTime and billing are built in, with client payments through the portal. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Confirmed in the analysis |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Amicus Cloud.
- Carried with mapping
- Filevine 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Amicus Cloud has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Amicus Cloud, and kept as the record of what was billed and held.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Amicus Cloud depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Amicus Cloud is kept running until the checks on Filevine are finished.
Where the data is now
Leaving Amicus Cloud
Little product documentation for Amicus Cloud is published today, so a move off it starts with looking at the firm’s own account, not a manual. What is actually there is listed in the analysis: matters, people, calendar entries, emails, time and bills. Anything beyond the modules the vendor named at launch, such as trust ledgers or stored documents, is confirmed from the live account before a destination is mapped.
Not the desktop Amicus
Three different things carry the Amicus name: this browser product, the Amicus Attorney desktop program, and Amicus Attorney running on a hosted desktop in Abacus Private Cloud. The browser product is not the desktop program under another name. The first step is confirming which one the firm signs in to, because a plan written for the desktop program does not fit this one.
Email sits in the product
Email is one of the modules on the Amicus Cloud dashboard, beside calendar and tasks. That raises a question a firm should settle early: which messages are attached to matters and need to travel with them, and which are simply the mailbox, which stays with the mail provider whatever happens to the practice system.
Billing without a visible ledger
Time entries and bills are inside Amicus Cloud. The public material does not say where the firm’s general ledger or trust records are kept. That is established in the analysis from the account and from the bookkeeper, since unpaid bills and any client money held must agree with the accounting records on the day of cutover.
Portal and APX payments
Clients may have been paying through the portal using APX. The card or bank details behind those payments belong to the payment service, not to the practice data, and do not move. Payment records against each bill can be carried. Clients on a recurring arrangement are identified so they can be set up again.
Where it is going
Arriving in Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Amicus Cloud holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 Cloud, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Filevine as a trial and checked against Amicus Cloud: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Amicus Cloud are frozen for an agreed window, the data is collected a final time and Filevine 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 Cloud as at the cutover date. Amicus Cloud 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 Cloud 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 Cloud holds
What is in it, how its records link, and where each piece would sit in Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Amicus Cloud to Filevine: what firms ask
Is Amicus Cloud the same thing as Amicus Attorney?
No. Amicus Attorney is a Windows program installed in the office or run on a hosted desktop. The Cloud product is separate, is used in a browser, and was called Amicus Online before 2020. A firm on one cannot assume that advice about the other applies to its data.
Is Amicus Cloud still being sold?
We cannot tell from public sources. CARET’s websites today present CARET Legal, AbacusLaw and Amicus Attorney, with no page for Amicus Cloud. A firm’s own agreement and account manager are the place to confirm its position. Either way, the planning for a move is the same.
What can we be sure will come across?
Before the analysis, only the obvious: matters, contacts, calendar entries, tasks, time and bills all have a place in any practice management system. For documents, trust records and anything the firm customised, the analysis shows what the account holds and where each item would sit in the destination.
Do trust balances in Amicus Cloud have a place in Filevine?
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 Cloud before the plan is fixed. If Filevine 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 Cloud have a place in Filevine?
Most of it does on paper. Documents, notes, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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 Filevine is kept as a readable archive, and you see which before the move.
What has to be decided before Amicus Cloud data is loaded into Filevine?
Time entries and billing records are carried with mapping, so each mapping is agreed with you first. Documents, notes, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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 Cloud and into Filevine
Other destinations from Amicus Cloud
Other systems that move into Filevine
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 Cloud and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Amicus Cloud to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.