Data migration route
LinkedIn data to Microsoft SQL Server
LinkedIn is a cloud contacts and calendar tool, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what LinkedIn holds and keeps it readable and open to queries.
LinkedInCloud- Contacts: Exported in full
Microsoft SQL ServerServer- 1 carried
What moves
What moves from LinkedIn to Microsoft SQL Server
Each row is a kind of record LinkedIn holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route one kind of record carries across.
| 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 placePeople and companies, with their roles on each matter. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against LinkedIn.
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
Not a new system. A complete copy the firm can query.
Writing LinkedIn out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in LinkedIn as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
LinkedIn is hosted by its maker and Microsoft SQL Server sits 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 Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what LinkedIn holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything LinkedIn holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against LinkedIn: record counts, totals where LinkedIn holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in LinkedIn, the export is run a final time and checked again. There is nothing to go live. LinkedIn is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Microsoft SQL Server. 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
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
LinkedIn to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold contacts from LinkedIn?
Yes. People and companies, with their roles on each matter. Contacts are written out with the rest, and counts and totals are agreed to the reports in LinkedIn as at the export date.
Does everything in LinkedIn have a place in Microsoft SQL Server?
On paper, yes: each kind of record LinkedIn holds has a place in Microsoft SQL Server. 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 is written out to Microsoft SQL Server?
Less than on most routes: each kind of record here is either exported or kept beside the data as files. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from LinkedIn and into Microsoft SQL Server
Other destinations from LinkedIn
Other systems that move into Microsoft SQL Server
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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from LinkedIn to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.