Data migration route
LinkedIn to Server drives migration
LinkedIn is a cloud contacts and calendar tool, 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.
LinkedInCloud
Server drivesFiles- Contacts: Kept as a readable archive
- 1 archived
What moves
What moves from LinkedIn to Server drives
Each row is a kind of record LinkedIn holds, whether Server drives have a place for it, and what is planned. On this route one kind has no place in Server drives and is archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | Held in partA member’s own first-degree connections: name, profile URL, company, position, date connected. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
What the plans mean
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without LinkedIn 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 LinkedIn 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 LinkedIn, 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.
LinkedIn 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 LinkedIn will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving LinkedIn
There is no firm-wide export from LinkedIn. Each lawyer requests an archive of their own account and receives a connections file. Those files are combined, checked against the contacts the firm already holds, and loaded as people with a company and a job title. It is a contact list and nothing more, and it is treated as one.
Each lawyer exports their own
The archive is requested from a member’s own settings, on a computer and not the mobile app, and the download link goes to that member’s primary email address and lasts 72 hours. Nobody else can request it for them. The firm collects one connections file per lawyer, and each file is labelled with whose network it is.
Email addresses are often missing
An email address is included only when the connection has chosen to let their connections download it. Many rows have a name, a company and a position, and no way to write to the person. Rows are matched to existing contacts by name and company, and the firm’s own record supplies the address.
Company and title go stale
The company and position columns show what each person’s profile said on the day of the export. People move firms. Where a contact already exists in the destination, the LinkedIn details are shown beside the firm’s own for someone to choose between, and nothing is overwritten without that choice.
Whose contact is it
A partner’s connections are their personal network, and some will not want every name visible to the whole firm. Before anything is loaded the firm decides whether these become shared firm contacts, private contacts of the lawyer, or a marketing list, and which lawyer is recorded as knowing each one.
Names in other scripts
LinkedIn’s help pages say the CSV format does not support every character, and names written in Chinese, Japanese or Hebrew script may not come through. Those rows are found by checking for blank or garbled names once the files are combined, and are corrected by hand from the profile address.
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 LinkedIn 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 LinkedIn: 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 LinkedIn, a final pass over a weekend picks up what changed since the trial. LinkedIn 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 LinkedIn 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 LinkedIn 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
LinkedIn to Server drives: what firms ask
Can the firm export all its lawyers’ connections at once?
No. LinkedIn provides each member’s own data to that member only, and lists only first-degree connections. Every lawyer runs the request from their own account and passes on the connections file. The files are then merged, and people known to several lawyers appear once with each relationship recorded.
Will LinkedIn messages come across?
The larger archive includes a messages file with dates, subjects and content. It is a member’s private correspondence and is rarely appropriate to load into a firm system. If a particular conversation matters to a file, the lawyer saves it to that matter by hand, the way they would a personal email.
Do contacts from LinkedIn arrive in Server drives without duplicates?
Server drives have no place for contacts. Can be kept only as an exported spreadsheet. The contact list from LinkedIn is exported as a spreadsheet and kept as a readable archive.
What happens to records Server drives have no place for?
On this route that is contacts. They are exported from LinkedIn 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 LinkedIn data is loaded into Server drives?
Less than on most routes: each kind of record here either carries across or is archived. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from LinkedIn and into Server drives
Other destinations from LinkedIn
Other systems that move 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.
LinkedIn and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from LinkedIn 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.