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

Data migration route

Coyote Analytics data to Microsoft SQL Server

Coyote Analytics is a server-based accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Coyote Analytics holds and keeps it readable and open to queries.

FromCoyote AnalyticsServer
  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. Custom fields: Exported with mapping
  11. Templates: Exported with mapping
  12. Emails: Confirmed in the analysis
  13. Notes: Confirmed in the analysis
  14. Trust money: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 8 carried
  • 3 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Coyote Analytics to Microsoft SQL Server

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

Records in Coyote Analytics and their place in Microsoft SQL Server
RecordIn Coyote AnalyticsIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldIncludes referral tracking and conflict searches.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocument numbering, indexing, OCR search and custom folder structures.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldSynchronises with Microsoft Exchange; calendar rules integration.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry, including a mobile app.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldHas a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTransactions and balances for look-up; it is not a trust accounting system.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable, budgeting and bank reconciliation.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partCustom fields on contacts.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument and email generation.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake and conflict approval workflows.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

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

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

Writing Coyote Analytics out to Microsoft SQL Server 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 Coyote Analytics 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.

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 Coyote Analytics stays untouched until the copy in Microsoft SQL Server has been checked.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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 Coyote Analytics holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Coyote Analytics 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 Microsoft SQL Server as a trial and checked against Coyote Analytics: record counts, totals where Coyote Analytics 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 Coyote Analytics, the export is run a final time and checked again. There is nothing to go live. Coyote Analytics 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 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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Coyote Analytics to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from Coyote Analytics?

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.

Does everything in Coyote Analytics have a place in Microsoft SQL Server?

Most of it does on paper. Emails, notes and trust ledgers 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Coyote Analytics is written out to Microsoft SQL Server?

Documents, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Emails, 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

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

Moving from Coyote Analytics to Microsoft SQL Server?

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

We reply within one business day.