skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.


This report is the second in a series which provides CSPs with guidance on how to migrate BSS to the cloud, including where to start, and lessons learned from the telecoms industry.


  • Identifying those systems that should be easiest to migrate and starting with these low-hanging fruits will help CSPs gain quick wins, gain their own lessons learned, and create momentum for expanding the scope of their migration project.

Features and Benefits

  • Compare the pros and cons of different cloud migration paths for systems in the BSS domain.
  • Learn from the experiences of CSPs and vendors that have already migrated systems in the BSS to the cloud.

Key questions answered

  • What are the different migration paths to the cloud?
  • How can I determine which cloud migration path is right for my systems?

Table of contents


  • Catalyst
  • Omdia view
  • Key messages


  • Recommendations for service providers
  • Recommendations for vendors

Revisiting the business impact of migrating BSS to the cloud

  • Conducting due diligence is essential to a successful migration
  • Committing to a “culture of cloud”

Determining the best migration path

  • Rehosting is the easiest path to the cloud, but not the best
  • Re-platforming can be an in-between option for those not quite ready for cloud-native
  • Re-factoring applications allows CSPs to take full advantage of cloud-native
  • Re-purchasing makes the most sense for EOL systems

Strategies for BSS migration

  • Multi-system migrations will yield better business outcomes than single system migrations
  • The most common BSS migration approach

Common roadblocks to a BSS cloud migration

  • Cloud security
  • Job security
  • The cost of cloud
  • Change management

Lessons learned from the telecoms industry

  • Lesson one: Start with the low-hanging fruit to generate momentum for the rest of the migration
  • Lesson two: Embracing out-of-the box product features lowers cost and ensures agility
  • Lesson three: Hybrid multi-cloud deployments help to mitigate concerns of vendor lock-in
  • Lesson four: Migrate the test environment to the cloud first
  • Lesson five: Path-to-production modeling can help determine if re-factoring is the right migration path


  • Further reading
  • Author