Data migration route
Salesforce to Server drives migration
Salesforce is a cloud 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.
SalesforceCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- 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 Salesforce to Server drives
Each row is a kind of record Salesforce 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.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAccounts and contacts, or person accounts for individuals. Leads are separate. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partSalesforce Files and older attachments linked to records. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails captured to a record are held as activity data. | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes on records. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | Held in partEvents are activities on records. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are activities on records. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and custom objects, plus objects added by installed apps. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partQuote templates. | 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 pipelines | HeldLeads, opportunities and campaign members. | No place | Kept 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 Salesforce.
- 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 Salesforce 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 Salesforce 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 Salesforce, 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.
Salesforce is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Salesforce will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Salesforce
Salesforce will hand over an entire org as a set of CSV files, one per object, through its Data Export service. Getting the data is rarely the problem. Understanding it is: which objects the firm really used, which fields were added by an app nobody remembers installing, and how records point to one another through their IDs.
The Data Export service
An administrator can export all data as a zip archive of CSV files, weekly or monthly depending on the edition, with options to include files, attachments and document versions. The archive is deleted 48 hours after it is ready, and a large org produces several zip files. Timing the final export around those limits is part of the cutover plan.
Formula fields are left out
Formula and roll-up summary fields are always excluded from exports, because they are calculated and not stored. A firm may rely on one without knowing it is a formula, such as a count of referrals from a contact. Those are identified in the analysis and either recalculated in the destination or captured through a report.
Accounts, contacts, person accounts
Salesforce separates the organisation, an account, from the people at it, contacts. Orgs that deal with individuals may use person accounts, which are both at once and appear in the account data and the contact data. Each client is resolved to one company or one person in the destination, with the record IDs used to avoid loading anyone twice.
Leads are not contacts
A lead is an enquiry kept in its own object, apart from accounts and contacts. Leads that never progressed are prospects the firm did not take on. They are moved to the destination’s intake area if it has one, kept as a marketing list, or left in the exported files.
Installed apps and legal layers
If the org runs a legal application built on the platform, the matters, parties and time entries live in that product’s custom objects, and its vendor’s documentation describes them. The move is then planned as a move off that product, with the standard Salesforce objects as supporting data.
Where it is going
Arriving in Server drives
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Salesforce 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.
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 Server drives and checked against Salesforce: 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 Salesforce, a final pass over a weekend picks up what changed since the trial. Salesforce 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 Salesforce 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 Salesforce 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.
- 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
Salesforce to Server drives: what firms ask
How do we get a full copy of our Salesforce data?
From Setup, an administrator with the Weekly Data Export permission runs Data Export and chooses Include all data, ticking the options for files and attachments. Salesforce emails a link to one or more zip files. That copy is taken once for the analysis and again at cutover.
Do our custom objects come across?
They are exported like any other object. Whether they have a home depends on the destination. A custom object that tracks referrals may map to a referral field. One that models something the new system has no idea of is carried as notes or kept in the export files, and the firm sees which before the move.
Do documents from Salesforce 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 Salesforce 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 Salesforce 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.
Other routes
Other routes from Salesforce and into Server drives
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.
Salesforce and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Salesforce 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.