Data migration route
GoldMine to Sync.com migration
GoldMine is a CRM and intake system, and Sync.com is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
GoldMineCRM and intake- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Sync.comCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 5 archived
What moves
What moves from GoldMine to Sync.com
Each row is a kind of record GoldMine holds, whether Sync.com has 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 Sync.com and are archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldContact records with custom fields. | No place | Kept as a readable archive |
| 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 placeFiles and folders within the path limit; some file types are skipped by the apps. | 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 partMessage files such as .msg or .eml, filed in the matter’s folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldA shared calendar of scheduled calls, appointments and other activities. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldActivities can be assigned to other users. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and screens are set up by the firm. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldTemplates for repeated documents and emails. | Has a place in partPrecedents load as ordinary files. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partSales opportunities with forecasting, marketing lists and campaign management. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against GoldMine.
- Carried with mapping
- Sync.com 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
- Sync.com 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.
Sync.com 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 Sync.com 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. Sync.com 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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what GoldMine holds and how it is organised, then agree with you where each kind of record will sit in Sync.com. 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 Sync.com 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 Sync.com. 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
Structure, permissions and handover
Sync.com 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.
A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
GoldMine to Sync.com: 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 Sync.com?
Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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 Sync.com has 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 Sync.com?
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.
Other routes
Other routes from GoldMine and into Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from GoldMine to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.