You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > RAW > Support > RAW Data FAQs > How Linkup Handles Company Mergers and Acquisitions
How Linkup Handles Company Mergers and Acquisitions
print icon

When a company is acquired, acquires another company, or is involved in a merger, Linkup must decide how to treat the Company IDs (CIDs) involved which best serves the data.  In this article, you will find scenario-based details that explain how companies are handled after an acquisition, merger, rebrand or spin-off occurs. 

 

Rebranding

 

When a company rebrands, LinkUp will update the name of the CID to match the new name of the rebranded company. For example, Facebook rebranded to Meta. In response, LinkUp updates the Facebook CID to Meta. The benefit of renaming the existing CID is that we keep the history and data tied to the same company, rather than creating a new CID for the same company but with a new name. 

 

Mergers

 

After a company completes a merger, LinkUp decides how to treat the CID by looking at how or where the jobs can be found for the new company. See below for three scenarios.

 

Merger Case 1: Company A and Company B merge to create Company C and the jobs for Company A and B are found on the ATS for Company C. 

Linkup Response: Create a new CID for Company C, keep Company A & B for historical records but remove jobs. 

 

Merger Case 2: Company A  and Company B merge to create Company C but the jobs were consolidated to either Company A or Company B's ATS but not both. 

Linkup Response: Create a new CID for Company C and migrate the scrape for the remaining ATS to the new CID. This response assumes the jobs are found entirely on either Company A's ATS or Company B's ATS but not both.

 

Merger Case 3:  Company A and Company B merge to create Company C but the jobs were not consolidated to a single ATS and remain in place on Company A and Company B ATS.

Linkup Response: Create a new CID for Company C and migrate the scrapes for both Company A and Company B ATS under the new CID for Company C.

 

Acquisitions

 

When one company acquires another, the way job postings are handled varies. Jobs may move to the parents company or to the child company or there may be no change at all. See below for three scenarios and how Linkup responds to company acquisitions.

 

Acquisition Case 1: Company A acquires Company B but the jobs for Company A remain on Company A's website and jobs for Company B remain on Company B's website. There is no change to how job openings are listed.

Linkup Response: Until there is a change to how the jobs are posted, Linkup does not make any changes.

 

Acquisition Case 2: Company A acquires Company B and moves job postings for Company B to Company A's ATS.

Linkup Response: Stop scraping Company B ATS and retire the CID, continue scraping jobs from Company A.  

 

Acquisition Case 3: Company A acquires Company B. Company A migrates job openings to Company B's ATS.

Linkup Response: Replace the code in the scrape at Company A with the code from Company B. Retire Company B.
 

 

Spin-Off Company

 

When a company spins off another company or service as a new company, Linkup will create a new CID for the new company and make no other changes. 

 

 

 

 

 

Feedback
0 out of 0 found this helpful

scroll to top icon