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

Data migration route

Affinity data to SQLite

Affinity is a practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Affinity holds and keeps it readable and open to queries.

FromAffinityPractice management
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Firm accounts: Exported in full
  8. Intake: Exported in full
  9. Documents: Exported with mapping
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 8 carried
  • 3 mapped
  • 2 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Affinity to SQLite

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

Records in Affinity and their place in SQLite
RecordIn AffinityIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldFacts and key dates are recorded on matters through DataForms.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldClients, contacts and suppliers in one central database.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldProfiled and full-text searchable, with versions linked to matters.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
EmailsEmails saved to matters or to the storeHeldFiled from Outlook, including by drag and drop.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCentral calendar that syncs with Microsoft Exchange and Outlook.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow tasks and ad hoc task lists.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTimers, fee sheets and charges raised automatically by workflow.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldIncludes consolidated, split, multi-party and multi-currency bills.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTrust transactions as rows, for look-up and not for accounting.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger across entities, branches and departments.Has a placeLedger journals as rows, where the source held them.Exported in full
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 placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldCentral precedent library, including email precedents.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partMarketing Matters runs campaigns as matters against the contact database.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Affinity.
Exported with mapping
SQLite 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
SQLite 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

Not a new system. A complete copy the firm can query.

Writing Affinity out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Affinity as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

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. Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Affinity stays untouched until the copy in SQLite has been checked.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Affinity holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Affinity holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against Affinity: record counts, totals where Affinity holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Affinity, the export is run a final time and checked again. There is nothing to go live. Affinity is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toSQLite

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

Structure, permissions and handover

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

Affinity to SQLite: 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.

Does the copy in SQLite hold trust ledgers from Affinity?

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.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. Notes and trust ledgers are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Moving from Affinity to SQLite?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.