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

Data migration route

Coyote Analytics to Server drives migration

Coyote Analytics is a server-based accounting and billing system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.

FromCoyote AnalyticsServer
  1. Documents: Carried across
  2. Templates: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Notes: Confirmed in the analysis
  5. Trust money: Confirmed in the analysis
ToServer drivesFiles
  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. Custom fields: Kept as a readable archive
  9. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 1 mapped
  • 3 to confirm
  • 9 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Coyote Analytics to Server drives

Each row is a kind of record Coyote Analytics holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, nine kinds have no place in Server drives and are archived and three kinds are confirmed in the analysis.

Records in Coyote Analytics and their place in Server drives
RecordIn Coyote AnalyticsIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldNo placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldIncludes referral tracking and conflict searches.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocument numbering, indexing, OCR search and custom folder structures.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files in each matter’s correspondence folder.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldSynchronises with Microsoft Exchange; calendar rules integration.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldNo placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry, including a mobile app.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeOnly as exported ledger reports kept as files.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable, budgeting and bank reconciliation.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partCustom fields on contacts.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partDocument and email generation.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake and conflict approval workflows.No placeKept as a readable archive

What the plans mean

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

An export the firm can open without the system.

Server drives hold files, and most of what Coyote Analytics holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Coyote Analytics, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Coyote Analytics holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against Coyote Analytics: 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 Coyote Analytics, a final pass over a weekend picks up what changed since the trial. 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 toServer drives

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 Server drives. 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

Server drives are 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.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Coyote Analytics to Server drives: 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 Server drives?

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 Server drives 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 Server drives have no place for?

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

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

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

Moving from Coyote Analytics to Server drives?

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

We reply within one business day.