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

Data migration route

Ciprocity to Smokeball migration

Ciprocity is a cloud case management system for legal aid work, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. Case records move into matters, and time, billing and trust are set up in Smokeball, often from a separate accounts package.

FromCiprocityCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried across
  9. Billing: Carried across
  10. Intake: Carried across
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToSmokeballDesktop and cloud
  • 10 carried
  • 2 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Ciprocity to Smokeball

Each row is a kind of record Ciprocity holds, whether Smokeball has a place for it, and what is planned. On this route ten kinds of record carry across, two kinds need mapping and two kinds are confirmed in the analysis.

Records in Ciprocity and their place in Smokeball
RecordIn CiprocityIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases with problem codes, funding codes, assignments, closing codes and outcomes.Has a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldOne contact can appear on many cases in different roles; aliases are kept.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldA documents browser on each case, with OCR run on scanned uploads.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeld in partInbound email from staff accounts threads into the case; SMS messages are kept too.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesHeldNotes are one kind of activity on the case.Has a placeAs memos; not importable on the Bill plan.Carried across
CalendarAppointments, court dates and deadlinesHeldAppointments and ticklers on a shared calendar, with iCal and Office 365 sync.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, and workflow rules that create them.Has a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime slips with activity type and funding source; optional supervisor approval.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeld in partNo client invoicing described; a grants manager keeps funder ledgers.Has a placeInvoices and billed invoice entries are on the import list.Carried across
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas 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 payablesTo be confirmedNo placeNo general ledger; the firm’s books stay in an accounting package.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields and case tabs built by the program’s administrator.Has a place in partValues need a matching field in the matter type’s layouts.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly from .docx and RTF templates, form letters and docassemble.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldPrescreen, eligibility against poverty guidelines, duplicate and conflict checks.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 Ciprocity.
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.

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Smokeball brings those two sources together. The case records come from Ciprocity. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Smokeball, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Ciprocity depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Ciprocity is kept running until the checks on Smokeball are finished.

Where the data is now

Ciprocity gives each program its own instance and database, so the data to be moved belongs to one customer and nobody else’s is mixed in. The record design is specific to legal aid. People are contacts with roles on cases, work is a single stream of activities, and nearly everything is coded for a funder. A destination outside legal aid needs most of that translated.

  1. Roles belong to the case

    A contact holds the name, phone and address. Whether that person is the client, the opposing party or opposing counsel is recorded on the case, and one contact can hold different roles on different cases. Systems that file a contact as a client or as an other party need a rule for people who have been both.

  2. One stream of activities

    Notes, time slips, ticklers and appointments are all activities and share one history on the case. A destination system will split them into file notes, time entries, tasks and calendar events. Each activity type is mapped separately, and the trial load is checked by counting each type per case, not just the total.

  3. Closed means a date

    A case counts as closed when Date Closed is filled in, and closing also records a closing code and an outcome. Changing the status alone does not close it. Cases with a closed-looking status and no date are found in the analysis and put right, or they will arrive in the new system as open work.

  4. Three assignment slots

    Each case has a Primary Counsel, a co-counsel and a third assignee that is labelled Case Manager unless the program renamed it. Pro bono attorneys and referral recipients can also be recorded. A destination with one responsible lawyer per matter needs somewhere for the others, usually as related staff or a custom field.

  5. Locked and approved time

    Older time periods are locked so that months already reported to funders stay closed, and where approval is used, approved entries cannot be edited in the ordinary way. That state is part of the record. Time is loaded with its funding source and its approval status so a past grant report can be matched to the hours behind it.

More about moving off Ciprocity

Where it is going

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.

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

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

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

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

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

More about moving into Smokeball

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

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Ciprocity, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Smokeball as a trial and checked against Ciprocity: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Ciprocity 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 Ciprocity as at the cutover date. Ciprocity 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 Ciprocity 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 fromCiprocity
Moving toSmokeball

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

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

Ciprocity to Smokeball: what firms ask

Our contacts appear on dozens of cases. Will they be duplicated?

They should arrive once each. A Ciprocity contact is a single record linked to every case it has a role on, so the load creates the contact first and then the links. Duplicates that already exist are a separate matter. A merge pass before extraction is worthwhile for those.

Can ethical walls be carried across?

The walls themselves are a security setting in Ciprocity and cannot be copied into another product. The list of who is walled off from which case can be. It is extracted with the cases and used to set restrictions in the new system before any user logs in, then tested with an account that should be blocked.

What about the HUD, VAWA and immigration modules?

These are optional modules with their own fields and reports, switched on per program. Their data sits on the case and is moved as fields. The reporting they produce, such as HUD 9902 submissions, is a function of the software. If the destination cannot produce it, that reporting needs another home before cutover.

Do trust balances in Ciprocity 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 Ciprocity 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.

Does everything in Ciprocity have a place in Smokeball?

Most of it does on paper. 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 Smokeball is kept as a readable archive, and you see which before the move.

What has to be decided before Ciprocity data is loaded into Smokeball?

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

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

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