Data migration route
LinkedIn to SharePoint migration
LinkedIn is a cloud contacts and calendar tool, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
LinkedInCloud- Contacts: Carried with mapping
SharePointCloud- 1 mapped
What moves
What moves from LinkedIn to SharePoint
Each row is a kind of record LinkedIn holds, whether SharePoint has a place for it, and what is planned. On this route one kind needs mapping.
| 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. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
What the plans mean
- 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.
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 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 SharePoint is limited before the export is copied in.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LinkedIn depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to LinkedIn is kept running until the checks on SharePoint are finished.
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 SharePoint
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what LinkedIn 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.
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 SharePoint 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 SharePoint. 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
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
LinkedIn to SharePoint: 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 SharePoint without duplicates?
SharePoint takes contacts in part. Only as rows in a list built for the purpose. The fields that have a place there are loaded after duplicates are merged where they can be identified. The rest of each contact record is kept as a note or in the archive.
Does everything in LinkedIn have a place in SharePoint?
On paper, yes: each kind of record LinkedIn holds has a place in SharePoint. 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 LinkedIn data is loaded into SharePoint?
Contacts 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 LinkedIn and into SharePoint
Other destinations from LinkedIn
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 SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from LinkedIn 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.