Stage 𝟏 Rebranding


This section outlines the rebranding process to bring Micro Focus products closer to the OpenText brand. To ensure a smooth and easy transition, the process will be divided into stages. We are now at Stage 1. Guidelines for the next stages will be communicated in the coming months, and this section will be updated accordingly.

Steps for rebranding

    1. What: Review the details of the Stage 1 rebranding in the section below. At a minimum, the Stage 1 updates listed in the requirements below should be made in the next major or minor release of each product.
    2. When: If teams can fit these updates into a release currently in process, without compromising the schedule or release requirements, then please do. If not, they should be added to the scope for the next major or minor release. If no major or minor release is planned, it is okay for the products to remain branded as Micro Focus for now. We will revisit the policy for those products on a quarterly basis.
    3. How: Some elements may not apply to some products. Please use the following checklists to track your implementation:
      Rebranding–UX checklist
      – Rebranding–Docs checklist
      Product managers have a task in P2M to confirm that Rebranding Stage 1 is completed prior to MR.
Stage 𝟏 checklist

Updated: November 1, 2023

Items that must be updated in the next major/minor release:

  1. All company name references (see Company name)
  2. OpenText logo should replace all Micro Focus logos (see Downloads).
  3. Masthead *
  4. Copyright notice
  5. About box *
  6. Sign-in screens *
  7. Installers *
  8. Splash screens *
  9. Favicons
  10. Micro Focus branded loaders
  11. Docs updates (see Docs guidelines here)
  12. HP/HPE Disclaimer text update
  13. Marketplace presence update
  14. CE branding *

* This item had been updated as part of the ‘CE branding’.

Out of scope for Stage 𝟏

Updated: November 1, 2023

Items that don’t need to be changed at this point:

  • Fonts
  • The following legal elements
    • EULA
    • Customer Terms
    • Additional License Authorizations (ALAs)
    • Service Descriptions for SaaS
    • Support standard terms
    • Professional services standard terms
  • URL domains (unless the product team has full control of creating the webpage)
  • Installation paths