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

Data migration route

GoldMine to Server drives migration

GoldMine is a CRM and intake system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.

FromGoldMineCRM and intake
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToServer drivesFiles
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Custom fields: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 3 mapped
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from GoldMine to Server drives

Each row is a kind of record GoldMine holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and five kinds have no place in Server drives and are archived.

Records in GoldMine and their place in Server drives
RecordIn GoldMineIn Server drivesWhat is planned
ContactsClients, other parties and referrersHeldContact records with custom fields.No placeCan be kept only as an exported spreadsheet.Kept 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 placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeldEmail is sent and received in the program and linked to the contact.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
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.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields and screens are set up by the firm.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldTemplates for repeated documents and emails.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 pipelinesHeld in partSales opportunities with forecasting, marketing lists and campaign management.No placeKept as a readable archive

What the plans mean

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

An export the firm can open without the system.

Server drives hold files, and most of what GoldMine holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used GoldMine, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.

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

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

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

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

Server drives store documents. Files in folders, named and dated during the load. 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 Server drives have no place for?

On this route that is contacts, calendar entries, tasks, custom fields 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 Server drives?

Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. 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 Server drives are the names and marks of their owners, used here only to identify the two systems.

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