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

Data migration route

Affinity to Box migration

Affinity is a practice management system, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from Affinity to Box

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

Records in Affinity and their place in Box
RecordIn AffinityIn BoxWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldFacts and key dates are recorded on matters through DataForms.No placeA matter is a folder, optionally with metadata; there is no matter record.Kept as a readable archive
ContactsClients, other parties and referrersHeldClients, contacts and suppliers in one central database.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldProfiled and full-text searchable, with versions linked to matters.Has a placeFiles and folders, named and dated as they are loaded.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook, including by drag and drop.Has a place in partAs .msg or .eml files in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents in the matter folder, not as a notes record.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCentral calendar that syncs with Microsoft Exchange and Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow tasks and ad hoc task lists.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTimers, fee sheets and charges raised automatically by workflow.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldIncludes consolidated, split, multi-party and multi-currency bills.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger across entities, branches and departments.No placeKept 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 place in partMetadata templates can hold fields such as matter number and client.Carried with mapping
TemplatesPrecedents, document templates and automationHeldCentral precedent library, including email precedents.Has a place in partPrecedents load as ordinary files; no document automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partMarketing Matters runs campaigns as matters against the contact database.No placeKept as a readable archive

What the plans mean

Carried across
Box has a place for this kind of record. It is loaded there and checked against Affinity.
Carried with mapping
Box 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
Box 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Affinity into Box means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Box does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Affinity.

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. Box 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’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.

  1. Decide who owns the top level

    Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.

  2. Restricted matters go near the top

    Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.

  3. Names Box will not accept

    Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.

  4. Matter details become metadata

    A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.

  5. File size follows the owner’s plan

    The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.

More about moving into Box

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Affinity holds and how it is organised, then agree with you where each kind of record will sit in Box. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Box and checked against Affinity: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Affinity, a final pass over a weekend picks up what changed since the trial. 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 toBox

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

Box is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.

What is agreed and set up

  • Top-level folder structure and who owns each folder
  • Groups for teams, mapped to collaborator roles
  • Metadata template for matter number, client and status
  • Shared link defaults and rules for external collaborators
  • Box Drive installed and signed in on each PC
  • Version limits and retention agreed with the firm’s records policy

Questions

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

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 Box 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 Box has no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, the firm’s accounts and intake records. 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 Box?

Emails, 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 decides which closed matters and how many versions of a document are in scope.

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

Moving from Affinity to Box?

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

We reply within one business day.