From LogoDIDACT to Relution: 10 steps to a successful MDM migration

With LogoDIDACT reaching the end of its life cycle on 31 December 2026, the pressure is mounting on schools and school authorities to take action. It is now crucial to plan the transition to a new mobile device management system well in advance – securely, in a structured manner and without unnecessary disruption to day-to-day school life.

Relution stands for data protection-compliant, platform-independent and efficient mobile device management – as well as for customer focus. To ensure that the transition from LogoDIDACT to Relution goes as smoothly as possible, we will actively support you right from the start.

Our promise to you:

• Support and advice throughout the entire migration process. This means you can draw on our experience whenever needed, and we’ll ensure a controlled transition.
• Cost-neutral migration terms for existing LogoDIDACT customers and partners.
• The tried-and-tested structure remains in place: LD Mobile is already powered by Relution technology. The switch does not mean a complete fresh start, but rather a direct transition to the underlying MDM solution.

During the transition phase to our platform, Relution offers you several options: you can take over standalone licences from Relution, arrange maintenance directly with Relution, and use all standard devices (iPhones, iPads, Android, Windows and Mac devices).

In addition to LogoDIDACT 4.0, other established school server solutions are also in use, depending on the federal state, the school’s organisational structure and its educational approach. These include, amongst others, solutions from the Baden-Württemberg State Media Centre (paedML), Univention, INL AG (Schulnetzpaket), H+H Software, Puavo and IST.

So set the course now, secure Relution’s support during the transition, and benefit from our MDM solution in the long term.

How does the switch from LogoDIDACT to Relution work in practice?

The Oberhavel district demonstrates how the migration can be successfully implemented in 10 steps. This practical example highlights what is important when planning, preparing for and carrying out an MDM switch. This case study offers particularly helpful insights for schools and school authorities planning their own transition.

Find out more in the video.

10 steps to a successful migration

Due to differing IT architectures and individual circumstances, every migration is unique. Nevertheless, key success factors can be defined regardless of these differences. We have put together a suggested 10-point plan to provide you with guidance on MDM migration and to outline an ideal process.

Use this practical guide to plan your migration safely, systematically and efficiently.

How to ensure a successful MDM migration:

1. Assess the current situation and clarify requirements

A clear overview is essential: Which schools are affected? How many devices, users and locations need to be taken into account? Which apps, policies and specific features are already in place and need to be migrated? Taking stock creates transparency and forms the basis for a successful migration.

2. Define the appropriate target structure

Before the technical transition begins, it should be clear what the future device management should look like. With Relution, different requirements can be managed centrally and in a multi-tenant manner within a single system. This makes the IT structure clearer and simplifies administration in the long term.

3. Involve all stakeholders at an early stage

A successful transition does not just affect the IT department. School management, IT managers, media coordinators, system administrators and other stakeholders should be informed and involved at an early stage. This creates a sense of security, promotes acceptance and makes implementation in day-to-day practice easier.

4. Start with a pilot phase

Before a full-scale roll-out, it is advisable to conduct a trial phase with selected schools. This allows processes to be tested, outstanding issues to be clarified and initial experience to be gained. This significantly simplifies the subsequent roll-out, as processes can be tested under real-world conditions and potential stumbling blocks identified at an early stage.

5. Prepare the technical infrastructure thoroughly

Careful preparation is a key factor in ensuring a smooth migration. This includes, amongst other things, setting up client accounts, preparing the environment in Apple School Manager, configuring certificates, directory services and device groups, and importing relevant settings. Good preparation saves time and effort later on.

6. Set standards and guidelines centrally

Global guidelines ensure consistency and reduce the administrative burden. These include, for example, Wi-Fi configurations, security policies, standard apps, role and permission structures, and consistent designs. In Relution, these can be managed centrally whilst still being customised individually.

7. Carry out the migration in a phased and planned manner

A successful migration takes place in clearly defined stages. Devices, users, licences and apps should be transferred, checked and reassigned in an organised manner. A structured process reduces risks and ensures that disruption to school operations is kept to a minimum.

8. Take specific requirements into account

Every school environment has its own particular characteristics. Parent-funded devices, specific app requirements or individual teaching approaches should be taken into account right from the migration planning stage. Relution offers the necessary flexibility to reliably accommodate these requirements too.

9. Empower those responsible and ensure support

To ensure that operations run smoothly after the migration, those involved should be given targeted support. This includes practical training, clearly defined responsibilities and well-coordinated concepts for permissions and roles. This creates reliable structures and plays a crucial role in ensuring the new solution is successfully embedded in day-to-day operations in the long term.

10. Continue to optimise after migration

The transition is not complete once the system goes live. After the migration, it is worth regularly reviewing and refining processes, policies and structures. Feedback and experience gained from day-to-day operations can be used to continuously optimise administration with Relution. This ensures that the new administrative environment can be operated stably in the long term and further developed in line with requirements.

To ensure the transition goes as smoothly and quickly as possible, we recommend planning as early as possible. Our Relution sales team will advise you on an individual basis and help you find the optimal solution for your requirements.