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

Data migration route

CollectMax to SimpleLaw migration

CollectMax is a server-based case management system for debt recovery work, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.

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. Trust money: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
  10. Emails: Confirmed in the analysis
  11. Calendar: Confirmed in the analysis
  12. Time and expenses: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 5 carried
  • 4 mapped
  • 4 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CollectMax to SimpleLaw

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

Records in CollectMax and their place in SimpleLaw
RecordIn CollectMaxIn SimpleLawWhat 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 placeCarried across
ContactsClients, other parties and referrersHeldDebtors, clients (creditors or forwarders), plaintiffs and other account members.Has a placeAs leads, clients or other contacts in the CRM.Carried 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 placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed 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 placeConfirmed 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 placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldCollection fee and suit fee invoices to clients, produced by remittance processing.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldA trust bank account with internal client accounts, monitored against overdraft.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partClient-specific user variables and firm-defined status codes.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldLetter and document templates, sent singly or in batches.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and intake forms.Confirmed in the analysis

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against CollectMax.
Carried with mapping
SimpleLaw 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
SimpleLaw has no place for it. It is exported in a format that opens without CollectMax 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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SimpleLaw brings those two sources together. The case records come from CollectMax. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SimpleLaw, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  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 SimpleLaw. 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 SimpleLaw as a trial and checked against CollectMax: record counts, trust and debtor 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 SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 toSimpleLaw

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

Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

CollectMax to SimpleLaw: 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 SimpleLaw?

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. They are exported from CollectMax 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 CollectMax data is loaded into SimpleLaw?

Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, calendar entries, time entries 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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from CollectMax to SimpleLaw?

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

We reply within one business day.