Data migration route
Coyote Analytics to NetDocuments migration
Coyote Analytics is a server-based accounting and billing system, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
Coyote AnalyticsServer- Documents: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 4 to confirm
- 6 archived
What moves
What moves from Coyote Analytics to NetDocuments
Each row is a kind of record Coyote Analytics holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, six kinds have no place in NetDocuments and are archived and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldIncludes referral tracking and conflict searches. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocument numbering, indexing, OCR search and custom folder structures. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email items profiled to the matter. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes are loaded as documents in the matter workspace. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldSynchronises with Microsoft Exchange; calendar rules integration. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense entry, including a mobile app. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, accounts payable, budgeting and bank reconciliation. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partCustom fields on contacts. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partDocument and email generation. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldClient intake and conflict approval workflows. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against Coyote Analytics.
- Carried with mapping
- NetDocuments 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
- NetDocuments 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
Only the documents have a place here.
NetDocuments is a document management system: it takes files and the details that describe them. Most of what Coyote Analytics holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Coyote Analytics produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
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. NetDocuments 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 Coyote Analytics
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Coyote Analytics holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into NetDocuments 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.
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
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 Coyote Analytics holds
What is in it, how its records link, and where each piece would sit in NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Coyote Analytics to NetDocuments: 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 NetDocuments?
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 NetDocuments 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 NetDocuments has no place for?
On this route that is contacts, calendar entries, time entries, billing records, the firm’s accounts 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 NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks 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.
Other routes
Other routes from Coyote Analytics and into NetDocuments
Other destinations from Coyote Analytics
Other systems that move into NetDocuments
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.
Coyote Analytics and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Coyote Analytics to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.