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

Data migration route

Amicus Attorney to Litify migration

Amicus Attorney is a server-based practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromAmicus AttorneyServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried across
  7. Intake: Carried across
  8. Emails: Carried with mapping
  9. Billing: Carried with mapping
  10. Custom fields: Carried with mapping
  11. Templates: Carried with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amicus Attorney to Litify

Each row is a kind of record Amicus Attorney holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.

Records in Amicus Attorney and their place in Litify
RecordIn Amicus AttorneyIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldHas a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldAttached to Files; Amicus-managed documents use check-in and check-out.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldEmails saved to Files; calendars and contacts sync with Exchange.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCourt rule sets can be added for rules-based dates.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partWith the Amicus Billing module; otherwise posted time goes to QuickBooks or PCLaw.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 balancesHeld in partTrust receipts, cheques and transfers come with Amicus Billing.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields, custom pages and Custom Records.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, plus Precedents that schedule a series of events.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried 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 placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Amicus Attorney.
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

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 Litify. 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 Attorney has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Amicus Attorney, and kept as the record of what was billed and held.

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. 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

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

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Litify

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 Attorney and checking each trial against Amicus Attorney.

  1. 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 Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. 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.

  3. Trial load

    The data is loaded into Litify as a trial and checked against Amicus Attorney: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Amicus Attorney 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 Attorney as at the cutover date. 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

Step 1 of 5: Start with the route

Moving fromAmicus Attorney
Moving toLitify

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 Litify. 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

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 Attorney to Litify: 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 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 Attorney 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 Attorney have a place in Litify?

Most of it does on paper. Notes and trust ledgers 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 Attorney data is loaded into Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and trust ledgers are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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 Litify are the names and marks of their owners, used here only to identify the two systems.

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