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

Data migration route

CollectMax to SmartAdvocate migration

CollectMax is a server-based case management system for debt recovery work, and SmartAdvocate is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.

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

What moves

What moves from CollectMax to SmartAdvocate

Each row is a kind of record CollectMax holds, whether SmartAdvocate has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and six kinds are confirmed in the analysis.

Records in CollectMax and their place in SmartAdvocate
RecordIn CollectMaxIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAccounts, each with one or more claims, a status code and links to related accounts.Has a placeCases by case type, with master and member relationships.Carried across
ContactsClients, other parties and referrersHeldDebtors, clients (creditors or forwarders), plaintiffs and other account members.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeld in partLetters and documents are generated per account or claim; stored files not confirmed.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeEmails are attached to cases.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldAccount notes, with colour-coded note indicators.Has a placeCarried across
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeAppointments and critical deadlines.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partMaxPlans schedule the documents due on each account.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeTracked time entries.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldCollection fee and suit fee invoices to clients, produced by remittance processing.Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldA trust bank account with internal client accounts, monitored against overdraft.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partClient-specific user variables and firm-defined status codes.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationHeldLetter and document templates, sent singly or in batches.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntake and lead records.Confirmed in the analysis

What the plans mean

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. CollectMax and SmartAdvocate may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in SmartAdvocate, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

CollectMax 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. SmartAdvocate 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 collections system does not look like a practice system. There is no matter with a client and a bill. There is an account with debtors and claims, a balance that grows with interest, payments that land in trust and a remittance that pays the client. Moving off it means deciding what a matter is before a single record is mapped.

  1. Accounts, debtors and claims

    One CollectMax account can hold several debtors and several claims, and each claim has a reference number that is usually the original creditor’s account number. A destination needs one matter per account or one per claim. The choice affects how balances, documents and court details divide, so it is tested on real accounts before it is fixed.

  2. Five-part claim balances

    A debt is kept as principal, interest, fees, costs and other, and interest can be projected forward. A general practice system has a debtor balance on an invoice and nothing like this. If the destination cannot calculate interest on a claim, the balance at cutover is loaded as a fixed figure with the rate and date noted.

  3. Remittance, not billing

    Debtor payments go into the trust bank account. Remittance processing then pays the client and raises the firm’s invoice for its collection fee, under whichever withholding arrangement that client has. This is the reverse of ordinary legal billing. Each client’s arrangement is recorded in the analysis, since the new system has to reproduce the same split.

  4. Client, forwarder and plaintiff

    The client on an account is either the creditor or a forwarder who sent the debt on, and a plaintiff may be attached separately. Three parties can stand where a practice system expects one client. All three are kept as linked contacts, and the one the firm reports and remits to becomes the client.

  5. Status codes and contact flags

    Status codes show where each claim is in the collection process and when it changed. Accounts also carry flags such as Do Not Contact, bankruptcy or a defending attorney, which stop letters being produced. Those flags protect the firm from contacting someone it must not. They are mapped first and checked on every trial load.

More about moving off CollectMax

Where it is going

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in CollectMax and checking each trial against CollectMax.

  1. Analysis

    We read what CollectMax holds and how its records link, then agree with you, field by field, where each piece will sit in SmartAdvocate. 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 CollectMax, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in CollectMax are frozen for an agreed window, the data is collected a final time and SmartAdvocate 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 CollectMax as at the cutover date. CollectMax 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 CollectMax 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 fromCollectMax
Moving toSmartAdvocate

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

    What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate

Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

CollectMax to SmartAdvocate: what firms ask

Can a general practice system run a collections practice?

Only with work. Matters, contacts and documents are no trouble. Interest on claims, payment posting in bulk, remittance to clients and electronic exchange with creditors are collections functions that most general systems lack. The analysis lists which of these the firm uses daily, and that list usually settles what kind of destination is realistic.

What happens to accounts with payment arrangements in progress?

They are the records to watch. Each has a balance, a payment history and a next expected payment. Where the destination takes payment history, it is loaded so the balance can be recalculated, not just stated. On the trial load, a sample of paying accounts is compared with CollectMax, including interest accrued to the day.

Do trust balances for each client carry over?

They are carried as opening balances, client by client. CollectMax keeps many clients’ money in one trust bank account through internal accounts, and the total of those must equal the bank balance on cutover day. That reconciliation is rehearsed on a full trial load first, because the financial cutover is not something to repeat.

Do trust balances in CollectMax have a place in SmartAdvocate?

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 CollectMax before the plan is fixed. If SmartAdvocate 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 CollectMax have a place in SmartAdvocate?

Most of it does on paper. Emails, calendar entries, time entries, trust ledgers, the firm’s accounts and intake records 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 SmartAdvocate is kept as a readable archive, and you see which before the move.

What has to be decided before CollectMax data is loaded into SmartAdvocate?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, calendar entries, time entries, trust ledgers, the firm’s accounts and intake records 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

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

Moving from CollectMax to SmartAdvocate?

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

We reply within one business day.