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

Data migration route

Affinity to SimpleLaw migration

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

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. Billing: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 7 carried
  • 3 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Affinity to SimpleLaw

Each row is a kind of record Affinity holds, whether SimpleLaw has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping, one kind has no place in SimpleLaw and is archived and three kinds are confirmed in the analysis.

Records in Affinity and their place in SimpleLaw
RecordIn AffinityIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldFacts and key dates are recorded on matters through DataForms.Has a placeCarried across
ContactsClients, other parties and referrersHeldClients, contacts and suppliers in one central database.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldProfiled and full-text searchable, with versions linked to matters.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 storeHeldFiled from Outlook, including by drag and drop.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCentral calendar that syncs with Microsoft Exchange and Outlook.Has a placeCarried 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 placeCarried across
BillingInvoices, payments and debtor balancesHeldIncludes consolidated, split, multi-party and multi-currency bills.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 balancesTo be confirmedHas a place in partTrust balances are supported; history depth is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger across entities, branches and departments.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
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 placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldCentral precedent library, including email precedents.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partMarketing Matters runs campaigns as matters against the contact database.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 Affinity.
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.
Kept as a readable archive
SimpleLaw has no place for it. It is exported in a format that opens without Affinity and handed to the firm as a read-only archive.

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

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

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

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

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

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

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

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

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

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

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

Affinity to SimpleLaw: 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 SimpleLaw?

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 SimpleLaw turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. They are exported from Affinity in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Affinity data is loaded into SimpleLaw?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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

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

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