Data migration route
GoldMine to Neos migration
GoldMine is a CRM and intake system, and Neos is a cloud case management system for personal injury work. Contacts and intake history move, and open enquiries become leads or cases in Neos.
GoldMineCRM and intake- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
NeosCloud- 6 carried
- 3 mapped
What moves
What moves from GoldMine to Neos
Each row is a kind of record GoldMine holds, whether Neos has a place for it, and what is planned. On this route six kinds of record carry across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldContact records with custom fields. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partDocuments on network drives are linked to contacts. The files stay where they were saved. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail is sent and received in the program and linked to the contact. | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldA shared calendar of scheduled calls, appointments and other activities. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldActivities can be assigned to other users. | Has a placeLoaded as checklist items. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and screens are set up by the firm. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldTemplates for repeated documents and emails. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partSales opportunities with forecasting, marketing lists and campaign management. | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Carried across |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against GoldMine.
- Carried with mapping
- Neos holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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
Intake history moves. The pipeline is rebuilt.
Intake data is the front end of a case. A lead in GoldMine carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Neos has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.
Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Neos or in the tool that feeds it.
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. Neos 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
Leaving GoldMine
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in GoldMine and checking each trial against GoldMine.
Analysis
We read what GoldMine holds and how it is organised, then agree with you where each kind of record will sit in Neos. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Neos 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what GoldMine holds
What is in it, how its records link, and where each piece would sit in Neos. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
GoldMine to Neos: 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 Neos?
Neos stores documents. Case Docs tab, organised in sub-tabs. 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.
Does everything in GoldMine have a place in Neos?
On paper, yes: each kind of record GoldMine holds has a place in Neos. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before GoldMine data is loaded into Neos?
Emails, 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.
Other routes
Other routes from GoldMine and into Neos
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
GoldMine and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from GoldMine to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.