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

Data migration route

GoldMine to SharePoint migration

GoldMine is a CRM and intake system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

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

What moves

What moves from GoldMine to SharePoint

Each row is a kind of record GoldMine holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, seven kinds need mapping and one kind has no place in SharePoint and is archived.

Records in GoldMine and their place in SharePoint
RecordIn GoldMineIn SharePointWhat is planned
ContactsClients, other parties and referrersHeldContact records with custom fields.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
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 libraries, with columns and versions.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, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldA shared calendar of scheduled calls, appointments and other activities.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldActivities can be assigned to other users.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldCustom fields and screens are set up by the firm.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates for repeated documents and emails.Has a place in partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against GoldMine.
Carried with mapping
SharePoint 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
SharePoint 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.

SharePoint holds 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 SharePoint 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. 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. SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 toSharePoint

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

SharePoint is 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.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

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

SharePoint stores documents. Files in libraries, with columns and versions. 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Contacts, emails, notes, calendar entries, tasks, custom fields 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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from GoldMine to SharePoint?

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

We reply within one business day.