SkillsInventory.comSKILLS TRACKING PLATFORM
Merging Two Companies' Skills Data After an Acquisition
Industry & Role Playbooks

Merging Two Companies' Skills Data After an Acquisition

Rovaryn Digital· November 17, 2026· 8 min read

Two skills files that don't line up

The deal closed on a Friday. By the following Wednesday, the integration lead had two files open: the acquirer's skills matrix, with 1–5 ratings and a column for each of 140 skills, and the acquired company's workbook, with free-text skill names, a three-level "Basic / Competent / Expert" scale, and a separate tab of certifications that nobody had touched since the last audit. A plant manager asked a simple question: who on the combined night shift is current on forklift evaluation? Nobody could answer it without opening both files, squinting at two different vocabularies, and guessing whether a blank cell meant "no" or "never assessed."

This is the ordinary state of skills data after a deal. Neither file is wrong. They just were never built to meet. By the end of this article you will be able to lay out a sequence for merging skills data after an acquisition, putting two inventories onto one taxonomy and one scale without losing a single certification record.

Why two skills spreadsheets don't simply stack

The tempting move is to paste one sheet beneath the other. It fails for three reasons that compound.

The vocabularies differ. One company says "Forklift Operation," the other says "Powered Industrial Truck – Sit-Down." One has "Customer Service," the other has "Client Relations" and "Account Support" as separate columns. A pivot table treats each as a different skill, so coverage looks thinner than it is for some skills and invisible for others.

The scales differ, and the same number means different things. A 4 from a manager who rates generously and a 4 from a manager who reserves it for the best person on the floor are not the same data point, even inside one company. Across two companies the gap is wider. Our guide to what a proficiency scale is covers why anchored definitions matter; after an acquisition they stop being a nicety and become the only way to compare people at all.

Blanks carry hidden meaning. In one workbook an empty cell may mean "not assessed." In the other, someone may have typed 0 for the same situation. Merge them and a 0 average can quietly drag down a skill nobody rated. Spreadsheets are also fragile at this scale of manual editing: a 2008 summary of Panko's research (Powell, Baker and Lawson, "Errors in Operational Spreadsheets") reports that 94% of spreadsheets contain at least one error, with an average cell error rate of about 5.2%. A merge touches nearly every cell, so it is exactly when you should expect to introduce more of them.

A plan for merging skills data after an acquisition

Work in this order. Each step produces something you can check before the next one begins.

1. Freeze both sources and take a snapshot

Copy both files as read-only originals and do all work in a third file. Record the date, the owner of each file, and how each was last updated. If a number in the merged inventory is ever questioned, you need to trace it back to a specific cell in a specific original.

2. Choose the target taxonomy

Pick one skills vocabulary and map both companies onto it. Do not pick "whichever is bigger." Pick whichever is most defensible and least dependent on either company's internal jargon.

The ONET database is a practical neutral option. It covers over 900 occupation profiles (also cited as close to 1,000 occupations), according to the ONET Resource Center at the U.S. Department of Labor, Employment and Training Administration, 2024. Its skills framework rates occupations on 35 standardized skill elements across 7 aggregated skill categories, per the U.S. Bureau of Labor Statistics' Monthly Labor Review (2021). ONET content is licensed under a Creative Commons Attribution 4.0 International License, so it is free to reuse with attribution (ONET OnLine, 2024). Because it belongs to neither merging company, using it avoids a quiet "they absorbed us" signal. Our O*NET taxonomy explainer walks through how the elements are organized.

Whatever you choose, keep company-specific skills too. A proprietary process or a customer-specific system will not appear in a public taxonomy, and it still matters for coverage.

3. Build a crosswalk before you move any data

A crosswalk is a simple table: source company, source skill name, target skill name, and a match type. Use four match types and nothing else:

  • Exact: the names mean the same thing.
  • Merge: several source skills map to one target skill.
  • Split: one source skill is too broad and maps to several targets.
  • No match: keep as a custom skill, flagged for review.

Have a manager from each side review the rows that are Split or No match. These are the judgment calls, and they should be made by people who know the work, not by whoever is holding the spreadsheet.

4. Reconcile the proficiency scales

Do not convert by arithmetic ("their 3 levels become 1, 3 and 5"). That creates precision that was never in the data. Instead, write behavioral anchors for your target 1–5 scale, then ask each team's managers to re-place their people against those anchors. For people nobody can re-rate quickly, carry the original rating forward in a separate column labeled with its source, and mark it as "legacy, unreconciled." That keeps the merged inventory honest about what has and hasn't been reviewed.

Worked example, with round numbers: if the acquired company's "Expert" covered roughly the top fifth of its operators and your 5 is reserved for the person others call for help, many "Experts" will land at 4 after review. That is expected, not an error.

5. Move certifications as records, not as skills

Certifications are where merges do the most damage, because they have dates and legal consequences. Keep each one as its own record: the person, the credential, the date earned, the expiry date, and the source file it came from. Do not collapse "forklift certified" into a skill rating.

For powered industrial truck operators, OSHA's powered industrial truck standard requires periodic re-evaluation and a certification record; check 29 CFR 1910.178(l) for the exact interval and record contents. If the acquired company's file stores only a "certified" checkbox, the evaluation date and evaluator may be missing, and you should find that out now rather than during an inspection. Confirm the current requirements with OSHA for your situation; this is not legal advice.

A tracking tool records self-reported certification data and expiry dates. It does not verify a credential with the body that issued it, so spot-check the originals for anything safety-critical. Our certification tracking guide covers the fields worth capturing.

6. Test the merged data before anyone relies on it

Run these checks on the combined inventory:

  • Count blanks and zeros per skill. A skill with many zeros and no blanks in one company's rows usually means blanks were converted on the way in.
  • Look for duplicate people. Employees who worked with both companies, or contractors, can appear twice under different names or IDs.
  • List every certification expiring within a year, and compare that list with each original file.
  • Sort skills by the number of people who hold them at a working level. Anything held by one person is a candidate for a coverage review, which is the subject of our piece on single points of failure in skills.

The Skills-Data Audit & Blank-vs-Zero Integrity Workbook is built for the blank-versus-zero part of this step: skills matrix in, data-quality problems out.

What to do in the first weeks after the merge

Once the merging of skills data after an acquisition is done and the inventory is clean, resist the urge to launch a big assessment program. Start by answering the three or four questions leadership actually asked: who can cover which critical skill at each site, which certifications lapse soon, and where is there no depth at all. A sequence for the early period is laid out in our first 30 days with a skills inventory.

Plan for a second pass, too. The first merge settles the vocabulary; a second review a few months in catches the skills people added when they realized the new taxonomy had no home for their work.

Where a spreadsheet stops being enough

For two small teams, the merged workbook is a reasonable home. If the combined organization is under roughly 50 employees, stay in Excel. Above that, the limits show up: spreadsheets offer no access control, no change history, and no automated alerts. When two companies each used a spreadsheet, the merged one inherits the weaknesses of both.

SkillsInventory is built for organizations in the 50–500 range. It ships with the O*NET taxonomy pre-loaded on first login, so there is no blank-slate taxonomy to design, and it sends automated certification-expiry emails at 90, 30 and 7 days. Pricing is flat-rate by tier rather than per seat, so growth from an acquisition does not add per-person charges, though you still need a tier that fits your combined headcount. It is deliberately narrow: skills inventory, gap analysis and certification tracking. HRIS and LMS integrations are not in the current product; they are deliberate non-goals for now, so plan to export from your HR system and load the data by CSV, on the tiers that include bulk CSV import.

If you would rather carry out merging skills data after an acquisition in a tool than in a workbook, you can start with the pricing tiers and a trial.

Ready to go beyond the guide?