Data migration route
Affinity to Smokeball migration
Affinity is a practice management system, and Smokeball is one that runs on the desktop and keeps its data in its maker’s cloud. Both run a whole practice, so this is a full move, and the financial records set the timetable.
AffinityPractice management- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
SmokeballDesktop and cloud- Firm accounts: Kept as a readable archive
- 9 carried
- 2 mapped
- 2 to confirm
- 1 archived
What moves
What moves from Affinity to Smokeball
Each row is a kind of record Affinity holds, whether Smokeball has a place for it, and what is planned. On this route nine kinds of record carry across, two kinds need mapping, one kind has no place in Smokeball and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldFacts and key dates are recorded on matters through DataForms. | Has a placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, contacts and suppliers in one central database. | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldProfiled and full-text searchable, with versions linked to matters. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook, including by drag and drop. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs memos; not importable on the Bill plan. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCentral calendar that syncs with Microsoft Exchange and Outlook. | Has a placeCalendar events and critical dates; plan limits apply. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldWorkflow tasks and ad hoc task lists. | Has a placeNot importable on the Bill plan. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers, fee sheets and charges raised automatically by workflow. | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| BillingInvoices, payments and debtor balances | HeldIncludes consolidated, split, multi-party and multi-currency bills. | Has a placeInvoices and billed invoice entries are on the import list. | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partMatter account balances load as opening balances; past transactions are not on the import list. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger across entities, branches and departments. | No placeNo general ledger; the firm’s books stay in an accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partDataForms hold matter-specific facts; how far firms define their own is confirmed in the analysis. | Has a place in partValues need a matching field in the matter type’s layouts. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldCentral precedent library, including email precedents. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partMarketing Matters runs campaigns as matters against the contact database. | Has a placeLeads are a record type of their own and can be converted to matters. | Carried across |
What the plans mean
- Carried across
- Smokeball has a place for this kind of record. It is loaded there and checked against Affinity.
- Carried with mapping
- Smokeball 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
- Smokeball 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 Smokeball 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. Smokeball 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
Leaving Affinity
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Smokeball
Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.
Every matter needs a type
Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.
The plan decides what loads
Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.
Leave auto-numbering until after
Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.
Documents arrive by folder
Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.
An opening balance per matter
Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Affinity holds and how its records link, then agree with you, field by field, where each piece will sit in Smokeball. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Smokeball as a trial and checked against Affinity: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Affinity are frozen for an agreed window, the data is collected a final time and Smokeball 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Affinity holds
What is in it, how its records link, and where each piece would sit in Smokeball. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Smokeball
Loaded data is not yet a working system. This is what NewLaw sets up in Smokeball, beyond the migration, so that people can work in it from the first day.
A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.
Set-up decisions in Smokeball
- Matter types in use, with default document folders for each
- Internal Reference format and the starting number for new matters
- Trust account details and the link to the accounting package
- Staff roles and permissions, including who sees billing and trust
- Firm precedents and letterhead rebuilt as Smokeball templates
- Desktop app, Word and Outlook add-ins on every PC
Questions
Affinity to Smokeball: 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 Smokeball?
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 Smokeball 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 Smokeball 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 Smokeball?
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.
Other routes
Other routes from Affinity and into Smokeball
Other destinations from Affinity
Other systems that move into Smokeball
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Affinity and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from Affinity to Smokeball?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.