Over the past few years, Planon has transformed Planon Universe into a powerful enterprise platform, offering increased flexibility, scalability, and connectivity in a standardized way. To unlock its full potential, we need your collaboration to prepare your customized software for compatibility with our new Planon Platform approach. This document explains the steps involved.

Planon Platform

A platform's true power lies in its capacity to foster growth by facilitating connections. Its value extends beyond its inherent features, as it thrives on its ability to seamlessly link external tools, teams, data, and processes. The Planon Platform embodies this principle. In this document, customized software implemented on this new platform is referred to as app(s). Reference to “SLA-TMS” means “Service Level Agreement Tailor-Made Software”.

Your action is needed to migrate customized software to app(s)

The Planon Platform comes with many advantages and to fully embrace the advantages offered, it is necessary to migrate all the customized software which is currently operating on the older platform.

Advantages of the new platform:

  • Customization: a customer can independently build their own apps or ask partners to build and deliver solutions in the form of apps
  • Better support: comprehensive documentation, how to guides, and Q&A forums are available for guidance
  • Improved development experience: automated building and publishing of apps, improved version support with app compatibility against Planon release
  • Flexibility: use own version of 3rd party libraries rather than Planon’s
  • Partner benefits: licensing support for partners and Planon
  • More powerful than before: dedicated IDE, predefined configurations, ability to configure free fields on demand, domain specific APIs, improved and new generic APIs like Event Connector, custom pages/dialogs/step views/gadgets (based on Wicket or Angular), mailers, event logging, local storages, talk workers, etc.

The objective is to complete the migration of all customized software under SLA-TMS by July 1, 2026 (Planon Live version 131). For cloud customers who have quarterly upgrades (i.e., no Upgrade Control contracted), the cut-off date is July 1, 2026 (Planon Live version 131). The customers who have contracted Upgrade Control will have a grace period of one year. The cut-off date for those customers will be July 1, 2027 (Planon Live version 143). During this one-year grace period, as long as the customers are on Planon Live version 130 or below, the customised software on the old platform will continue to work.

a) For customized software developed for you by Planon, and if you have contracted with Planon to provide SLA-TMS, Planon will facilitate the migration. The migration process of customized software from the old platform to app(s) on the new platform will commence on July 15, 2024. The objective is to complete the migration of all customized software under SLA-TMS by the timelines mentioned above. Planon will generally migrate customers in the order determined by Planon, after considering customer upgrade windows and other constraints. However, customers can request prioritisation, which will be considered on a case-by-case basis. Customer will be well informed before the migration starts. Please reach out to your Account Manager to learn the timelines of your customised software migration to app(s) on the new platform.

b) For customized software developed by Planon for you, in the case you have NOT contracted with Planon to provide SLA-TMS, please be aware that from Planon Live Version 131, customized software systems on the old platform will no longer be operational. It is the customer's responsibility to reach out to Planon and facilitate the migration by the timelines mentioned above. This enables the continued functionality and compatibility of these systems within the new platform environment. If you need support for this, please reach out to your Account Manager to determine whether we can help you.

c) For customized software developed by the customer, please be aware that from Planon Live Version 131, the customized software systems on the old platform will no longer be operational on the latest version of the Planon Software. It is the customer's responsibility to facilitate the migration by the timelines mentioned above. This ensures the continued functionality and compatibility of these systems within the new platform environment. If you need support for this, please reach out to your Account Manager.

Migration criteria

Overview of the migration from customized software to Planon Platform.

  • If the customer has implemented the customized software on the old platform and is responsible for its maintenance, then the customer is required to handle the migration.
  • If Planon has implemented the customized software on the old platform and there is no SLA-TMS contract in place, then the customer must facilitate the migration by reaching out to Planon’s Account Manager.
  • If Planon has implemented the customized software and there is an SLA-TMS contract in place, then Planon will oversee the migration.

    Impact to customer

    • When we need to re-deploy or re-configure, there might be some downtime, and the duration will depend on how many solutions need to be converted. Planon will plan this in collaboration with the customer.
    • In some cases, it might not be possible to migrate certain components exactly as they are. In such instances, Planon will collaborate with the customer to discuss the necessary functionality and rebuild it accordingly.
    • If a third party is involved and a solution must be rebuilt from scratch, the customer will need to arrange meetings with the third-party vendor.

      Customer involvement

      Regarding customer involvement during the conversion process:

      • We encourage discussions about potential improvements or modifications to existing solutions.
      • The customer's participation is vital in testing and providing acceptance for the converted solutions.
      • We greatly appreciate the support provided by the customer during the implementation phase.

        Planon involvement

        For the customized software developed for you by Planon where you have contracted with Planon to provide SLA-TMS, Planon will assist the customer with the entire project, from analysis to delivery. In collaboration with the customer, Planon will determine what can and cannot be migrated on solutions for the latter. Once this has been determined, Planon will deliver the project, enabling customer acceptance testing for the app(s), and offers post-production support as needed as part of the SLA-TMS.

        We appreciate your willingness to work together on this!