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

Data migration route

Affinity to Litify migration

Affinity is a 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.

FromAffinityPractice management
  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
  14. Firm accounts: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Affinity to Litify

Each row is a kind of record Affinity 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 three kinds are confirmed in the analysis.

Records in Affinity and their place in Litify
RecordIn AffinityIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldFacts and key dates are recorded on matters through DataForms.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClients, contacts and suppliers in one central database.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldProfiled and full-text searchable, with versions linked to matters.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook, including by drag and drop.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 notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCentral calendar that syncs with Microsoft Exchange and Outlook.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow tasks and ad hoc task lists.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers, fee sheets and charges raised automatically by workflow.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldIncludes consolidated, split, multi-party and multi-currency bills.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 balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger across entities, branches and departments.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partDataForms hold matter-specific facts; how far firms define their own is confirmed in the analysis.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldCentral precedent library, including email precedents.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partMarketing Matters runs campaigns as matters against the contact database.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 Affinity.
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 Affinity 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 Affinity, and kept as the record of what was billed and held.

How Affinity is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Affinity 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

Affinity firms tend to use the whole system, ledger included. A move therefore covers more than matters and documents: the general ledger, the safe custody register, workflow procedures and a precedent library all need an answer in the destination. The analysis also establishes where the database and document store are hosted, since that decides how the data is collected.

  1. A safe custody register

    Affinity keeps safe custody records linked to contacts, clients and matters: the wills, deeds and other originals the firm holds. Many newer systems have no register of this kind. Where the destination lacks one, the records are loaded as a custom record type or kept as a controlled list, and the firm chooses which before the trial.

  2. DataForms hold the facts

    Matter-specific facts and key dates are entered through DataForms. They are the nearest thing Affinity has to custom fields, and automated documents draw on them. Each form in real use is listed with its fields, then mapped to fields in the new system. Forms that only a handful of old matters used are usually carried as a note.

  3. The ledger is inside

    The general ledger is part of Affinity, with budgets and reporting across entities, branches and departments, and consolidated reporting for a service company. If the new system has no ledger, the firm is also setting up an accounting package. Opening balances are agreed for each entity separately, and prior-year figures stay in the archive.

  4. Documents found by profile

    Staff find documents by context, purpose and title, or by searching the full text, and sensitive matters can be locked down with document profiles and team security. A destination built on folders needs a folder for each document. The profile is used to derive it, and restricted matters are flagged so their access rules are rebuilt first.

  5. Campaigns stored as matters

    Marketing Matters runs each campaign as a separate project, which Affinity treats as a matter. Those are not client files. They are separated out during the analysis so they do not arrive in the new system as legal matters with no client, and the contact lists behind them are exported for the firm’s marketing tool.

More about moving off Affinity

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

  1. Analysis

    We read what Affinity 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 Affinity, 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 Affinity: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

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

Affinity to Litify: what firms ask

Does our safe custody register move?

The records move if the new system has somewhere to hold them. Each entry is exported with the client and matter it is linked to. Where the destination has no register, the choice is between a custom record type there and a list the firm keeps beside it, and that is settled in the analysis. The packets themselves do not change, so the register must still match the strongroom.

We run two entities in Affinity. Can they stay separate?

They can, provided the destination or its accounting package supports more than one entity. Each entity’s matters, debtors and ledger balances are extracted and reconciled on their own. If the new system holds one entity per account, the firm may need two accounts, and that is settled during the analysis.

What happens to our workflow procedures?

They are rebuilt, not converted. Affinity’s procedures link tasks to drafting, searches and automatic charges, and no other product reads them. The procedures in real use are listed with what each step does, and the equivalent is set up in the new system’s workflow tool where it has one. Steps nobody follows any more are dropped with the firm’s agreement.

Do trust balances in Affinity 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 Affinity 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 Affinity have a place in Litify?

Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 Affinity 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, trust ledgers and the firm’s accounts 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

Affinity and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Affinity 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.