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

Data migration route

Smokeball to NetDocuments migration

Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

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

What moves

What moves from Smokeball to NetDocuments

Each row is a kind of record Smokeball holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, seven kinds have no place in NetDocuments and are archived and one kind is confirmed in the analysis.

Records in Smokeball and their place in NetDocuments
RecordIn SmokeballIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach has a matter type for an area of law and a jurisdiction; the number is the Internal Reference.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 referrersHeldContacts hold roles on matters.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldFiles and folders inside each matter, with version history and full-text search.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to the matter from Outlook, with attachments linked to the email.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeldFile notes are called memos.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldEvents linked to matters, synced with Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks and workflows.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldEntered by hand or captured automatically by AutoTime.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust accounts with reconciliation and protected funds.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partFields come from each matter type’s layouts; firm-added fields are confirmed in the analysis.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldA precedent library of forms and templates that fill from the matter.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 pipelinesHeldLeads, and intake forms made in a form builder.No placeKept 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 Smokeball.
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 Smokeball 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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Smokeball is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Smokeball for matters and billing, or into an archive.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Smokeball depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Smokeball is kept running until the checks on NetDocuments are finished.

Where the data is now

Smokeball keeps its data in its own cloud, so a move off it starts with getting a full copy out: matter and contact lists, the files in every matter, and the billing and trust reports. Its reports export contacts and matters to CSV. The detail that takes the time is the matter-type fields, which differ from one kind of matter to the next.

  1. Fields belong to the matter type

    Matter details are held in layouts, such as Case Details or Property Details, and the set of layouts depends on the matter type. A family matter and a conveyance have different fields. The extract has to be taken type by type, and each layout mapped to custom fields or a note in the new system.

  2. Internal Reference is the number

    What other systems call a matter number, Smokeball calls the Internal Reference. It can be typed by hand or generated from parts, with a counter that some firms reset each calendar year, and individual matters can be overridden. We test the references for duplicates and gaps before using them as the key that documents are matched on.

  3. Memos, and emails with attachments

    File notes are memos. Emails saved from Outlook sit in the matter with their attachments, and each attachment keeps a link back to the email it arrived on. Most destinations store the email and the attachment as two unrelated files. Both come across, but that link is generally lost unless the attachment stays inside the email file.

  4. Version history stays behind

    Smokeball keeps earlier versions of a file and lets users compare and restore them. A bulk copy of the documents takes the current version of each. If earlier versions of particular documents matter, for instance negotiated contracts, the firm names those matters and the versions are pulled out for them as separate files.

  5. No ledger to move

    There is no general ledger in Smokeball. Billing and trust are inside it, and transactions are passed to a linked accounting package: MYOB or Xero in Australia, QuickBooks Online in the US. So the firm’s books stay where they are. What changes is the feed into them: the new system has to be connected to the same accounts from an agreed date.

More about moving off Smokeball

Where it is going

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.

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

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

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

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

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

More about moving into NetDocuments

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.

  1. Analysis

    We read what Smokeball 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.

  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 NetDocuments and checked against Smokeball: 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 Smokeball, a final pass over a weekend picks up what changed since the trial. Smokeball 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 Smokeball 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 fromSmokeball
Moving toNetDocuments

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

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

Smokeball to NetDocuments: what firms ask

Can we take our Smokeball matter numbers with us?

Yes in most cases. The Internal Reference is exported with each matter and loaded as the matter number wherever the destination accepts one. If the counter was reset each year, the reference needs its year component to stay unique. We check that before the trial load and report any references used twice.

Do closed matters need to move?

They do not have to. Closed matters can move as full records, as documents only, or stay in the archived copy. The choice turns on how often the firm reopens old files and on its retention obligations. Archive details recorded when a matter was closed are captured in the analysis so they are not lost.

Our office accounts are in a separate accounting package. Does anything happen to them?

The ledger stays in that package. Smokeball has been sending it invoices and payments, and that feed stops at cutover. The new system is connected to the same file from an agreed date, with the account mapping checked on a trial so double posting shows up before go-live. Which system produced each entry is then clear from its date.

Do trust balances in Smokeball have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Smokeball 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 NetDocuments has no place for?

On this route that is contacts, notes, calendar entries, time entries, billing records, trust ledgers and intake records. They are exported from Smokeball 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 Smokeball data is loaded into NetDocuments?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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

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

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