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

Data migration route

GoldMine to NetDocuments migration

GoldMine is a CRM and intake 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.

FromGoldMineCRM and intake
  1. Documents: Carried across
  2. Emails: Carried across
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
  5. 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. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 2 mapped
  • 1 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from GoldMine to NetDocuments

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

Records in GoldMine and their place in NetDocuments
RecordIn GoldMineIn NetDocumentsWhat is planned
ContactsClients, other parties and referrersHeldContact records with custom fields.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partDocuments on network drives are linked to contacts. The files stay where they were saved.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldEmail is sent and received in the program and linked to the contact.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeldNo placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldA shared calendar of scheduled calls, appointments and other activities.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldActivities can be assigned to other users.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields and screens are set up by the firm.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates for repeated documents and emails.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 pipelinesHeld in partSales opportunities with forecasting, marketing lists and campaign management.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 GoldMine.
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 GoldMine 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 GoldMine 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 GoldMine 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.

How GoldMine is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. GoldMine 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

GoldMine keeps its data in a SQL Server database that the firm usually owns and hosts, so the firm holds the data itself. The work is in what surrounds the contacts: completed activities going back years, email that was sent and received inside the program, and documents that are linked by file path to a network drive.

  1. Email lives inside GoldMine

    GoldMine has its own mail client, and some users send and receive all their work email in it. Messages handled that way are linked to contacts in GoldMine and may not be in Outlook at all. They are extracted with their contact links and either filed to matters in the destination or loaded into the users’ mailboxes.

  2. Linked documents are paths

    A document linked to a contact is a pointer to a file on a network drive. If the drive letter changed or a folder was tidied up, the link is dead. Each link is tested against the file system before the move, and the firm gets a list of links that no longer resolve.

  3. Pending and completed activities

    Scheduled calls, appointments and next actions sit in the calendar until completed, then pass into the contact’s history. A long-running database holds far more history than live activity. The firm decides how many years of history to carry as dated notes and whether future activities become tasks or calendar entries.

  4. Screens changed over the years

    Firms customise GoldMine heavily, relabelling fields and adding their own. The label on screen may bear no relation to the field name in the database. Field mapping is done from the screen designs with someone who uses the system daily, not from the database column names alone.

  5. Hosted copies

    GoldMine Cloud is the desktop program running on a hosted machine with its own SQL Server. The data has the same shape as an on-premises installation, but getting a backup means arranging access with whoever hosts it. That request is made early, since everything else waits on it.

More about moving off GoldMine

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

GoldMine to NetDocuments: what firms ask

Who do we need to ask to get our data out of GoldMine?

Usually nobody outside the firm. An owned installation keeps its SQL Server database on the firm’s own server, and the firm’s IT provider can take a backup. For GoldMine Cloud the hosting provider supplies it. The backup and the linked document folders together are what the analysis starts from.

Can linked emails be kept with the right client?

Emails linked to a contact keep that link when extracted, so they can be matched to the same person in the new system. Getting them onto the right matter is harder, because GoldMine links to contacts, not matters. Rules based on date ranges and correspondents are agreed, and unmatched email stays on the client.

Do documents from GoldMine keep their folders and dates in NetDocuments?

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

What happens to records NetDocuments has no place for?

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

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

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

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