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

Data migration route

CollectMax to Server drives migration

CollectMax is a server-based case management system for debt recovery work, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromCollectMaxServer
  1. Documents: Carried across
  2. Notes: Carried with mapping
  3. Templates: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Calendar: Confirmed in the analysis
  6. Time and expenses: Confirmed in the analysis
  7. Intake: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Trust money: Kept as a readable archive
  6. Firm accounts: Kept as a readable archive
  7. Custom fields: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 2 mapped
  • 4 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CollectMax to Server drives

Each row is a kind of record CollectMax holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, seven kinds have no place in Server drives and are archived and four kinds are confirmed in the analysis.

Records in CollectMax and their place in Server drives
RecordIn CollectMaxIn Server drivesWhat 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.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldDebtors, clients (creditors or forwarders), plaintiffs and other account members.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partLetters and documents are generated per account or claim; stored files not confirmed.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 notesHeldAccount notes, with colour-coded note indicators.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partMaxPlans schedule the documents due on each account.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeOnly as exported reports or spreadsheets.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 as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldA trust bank account with internal client accounts, monitored against overdraft.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partClient-specific user variables and firm-defined status codes.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldLetter and document templates, sent singly or in batches.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 pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from CollectMax into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in CollectMax.

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 CollectMax stays untouched until the copy in Server drives has been checked.

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

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 CollectMax 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 CollectMax: 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 CollectMax, a final pass over a weekend picks up what changed since the trial. 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 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 CollectMax 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

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

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from CollectMax are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Server drives have no place for?

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

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

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

Moving from CollectMax 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.