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

Data migration route

Coyote Analytics to Smokeball migration

Coyote Analytics is a server-based accounting and billing system, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. The financial records lead: balances and open items move, and the matters in Smokeball are built around them.

FromCoyote AnalyticsServer
  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. Billing: Carried across
  8. Intake: Carried across
  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
ToSmokeballDesktop and cloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Smokeball
  • 8 carried
  • 2 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Coyote Analytics to Smokeball

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

Records in Coyote Analytics and their place in Smokeball
RecordIn Coyote AnalyticsIn SmokeballWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeEach needs a Smokeball matter type; leads import alongside matters.Carried across
ContactsClients, other parties and referrersHeldIncludes referral tracking and conflict searches.Has a placeMatter roles import on the Grow and Prosper+ plans only.Carried across
DocumentsFiles stored in or linked from the systemHeldDocument numbering, indexing, OCR search and custom folder structures.Has a placeFiles and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeKept in the matter with other files.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeAs memos; not importable on the Bill plan.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldSynchronises with Microsoft Exchange; calendar rules integration.Has a placeCalendar events and critical dates; plan limits apply.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeNot importable on the Bill plan.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry, including a mobile app.Has a placeUnbilled time, fee and expense entries, with activity codes.Carried across
BillingInvoices, payments and debtor balancesHeldHas 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 payablesHeldGeneral ledger, accounts payable, budgeting and bank reconciliation.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 itselfHeld in partCustom fields on contacts.Has a place in partValues need a matching field in the matter type’s layouts.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument and email generation.Has a placeFirm precedents are rebuilt as Smokeball templates.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake and conflict approval workflows.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 Coyote Analytics.
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 Coyote Analytics 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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Coyote Analytics needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Coyote Analytics. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Smokeball are agreed to the trial balance and aged debtors from Coyote Analytics as at the cutover date, and that load is rehearsed before it is done for real.

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

A firm leaving Coyote is moving its accounting system, and often its conflicts database and document index as well. The financial data is the centre: unbilled time and costs, invoices and receipts, the general ledger and payables. Which of the practice modules were really used varies firm to firm, so the analysis starts by finding out which ones hold live records.

  1. Find the live modules

    Coyote was sold as modules, and a firm may have run the financial side with another product for documents and calendars. A module holding a few hundred old records is treated differently from one in daily use. Record counts and last-used dates for each module are the first thing reported back.

  2. Budgets at three levels

    Budgets can be kept on the general ledger, on timekeepers and on individual client matters, with alerts. A matter budget is often something the client was promised. Budgets are extracted with the matter, and loaded where the destination has a budget field or carried as a note where it does not.

  3. Allocations and profitability

    Profitability reports for timekeepers and practice areas depend on direct and indirect allocation rules set up in Coyote. Loading the transactions elsewhere does not bring the rules with them. The rules are written down during the analysis so the same view can be rebuilt in the new reporting tool.

  4. Records and containers

    Records management tracks physical containers, the documents in them and where each is stored. That is the firm’s index to its boxes. Few practice systems have a place for it. It usually comes across as a field or note on the closed matter, or as a register the records clerk keeps.

  5. Hosted or on your server

    Firms on the original version hold the database on their own server. Those on Coyote Analytics Cloud have it hosted by the vendor on Amazon Web Services and reach it through a browser. How a copy of the data is obtained differs between the two, and is arranged at the start.

More about moving off Coyote Analytics

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 Coyote Analytics 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 Coyote Analytics, 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 Coyote Analytics: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Coyote Analytics 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 Coyote Analytics as at the cutover date. Coyote Analytics 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 Coyote Analytics 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 fromCoyote Analytics
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 Coyote Analytics 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

Coyote Analytics to Smokeball: what firms ask

Is Coyote Analytics now SurePoint Finance Core?

SurePoint bought Coyote Analytics in June 2022 and said it would stay a standalone product. The old Coyote web address now leads to SurePoint’s Finance Core page, where customers quoted still call it Coyote. Your contract and login screen show which name applies to you. The data is the same under both.

Do we keep our client and matter numbers?

Client and matter numbers are carried exactly where the destination lets the firm set them. Where it generates its own, the Coyote number goes into a reference field that staff can search. Accounts staff tend to know matters by number, so this is settled early.

Can our client billing rules move?

The invoices already sent do not need to. What moves is the set-up behind them: task and activity codes, timekeeper classifications, client billing rules and rates. These are extracted as lists and rebuilt in the destination, then tested with one real client before the first live bill run.

Do trust balances in Coyote Analytics 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 Coyote Analytics 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 Coyote Analytics 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 Coyote Analytics data is loaded into Smokeball?

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

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

Moving from Coyote Analytics 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.