What does re-licensing mean for a company's SOPs, documents and code?
Re-licensing means the data for a deal already exists. Much of a company's data already lives in third-party software. Licensing it means re-licensing what already exists, and getting paid for it rather than giving it away for free. No new data collection is needed. Procedures in a wiki, answers in a help desk, and code with its review history in a repository can each be described and licensed without collecting anything new. The same data can also be licensed again later, to a new buyer or under a renewal. In software, re-licensing more often means changing the license a work is distributed under, which is a different question.
Is re-licensing the same as sublicensing?
No. Re-licensing is the owner licensing its own data again; sublicensing is a licensee passing the rights it received on to someone else. micro1's standard grant lets the buyer sublicense "through multiple tiers" (micro1, s. 1.2), while Tempus's 2026 neurology deal used a side letter confirming Tempus's consent to one named sublicense (Tempus 8-K, Oct 23 2026). A sublicense you allow is a license you are not paid for directly, unless the contract says otherwise.
What should you check before re-licensing?
Check that you hold the rights and that earlier deals allow it. A buyer's terms may ask you to warrant that you created the data or have obtained "all necessary rights, consents and licenses" (micro1, s. 5.2), so read your software vendors' terms and any earlier data license for limits on reuse, exclusivity or field of use. Under micro1's terms a buyer may not resell the same data "as a standalone data product" (micro1, s. 1.4), but it can still sublicense it, so an earlier buyer's customers may already hold rights to the data you plan to license again. Your company can be paid more than once, through renewals and repeat licences.
General information, not legal advice.