Data migration route
LinkedIn to Gladiate migration
LinkedIn is a cloud contacts and calendar tool, and Gladiate is a cloud case management system for personal injury work. This is a narrow move: the records LinkedIn holds are matched to the people and matters in Gladiate.
LinkedInCloud- Contacts: Carried across
GladiateCloud- 1 carried
What moves
What moves from LinkedIn to Gladiate
Each row is a kind of record LinkedIn holds, whether Gladiate 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 placeClients, leads and referral sources. | Carried across |
What the plans mean
- Carried across
- Gladiate 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
A narrow move, checked like a large one.
A source like LinkedIn holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Gladiate, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.
The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Gladiate already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.
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 Gladiate 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 Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Gladiate 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 Gladiate. 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 Gladiate 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 Gladiate. 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
Setting up Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
LinkedIn to Gladiate: 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 Gladiate without duplicates?
Gladiate has a place for contacts. Clients, leads and referral sources. Duplicates are merged in LinkedIn before extraction where they can be identified, and the list is matched against contacts already in Gladiate. It is not always possible to find every one, so some may carry across.
Does everything in LinkedIn have a place in Gladiate?
On paper, yes: each kind of record LinkedIn holds has a place in Gladiate. 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 Gladiate?
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 Gladiate
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 Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from LinkedIn to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.