Nowadays, companies are visiting the idea of getting their apps to the cloud. For years, it was thought that Domino apps migration to the cloud would be impossible. We have alreadydemonstrated that this is not true.
You might think that it’s great that you can migrate your mail, but what do you do with the apps that are still bringing profit and are used by a large number of people. As the environment changed, the need to migrate Domino apps as well became more and more obvious.
What can you do to solve this dilemma? Well, you can take the app, run it in the IBM Cloud infrastructure and you still own the app but all the maintenance is made by the company which helps you with the migration.
Most apps today are relatively fluid so it’s relatively easy to migrate it from one environment to another.
So, you decided that it’s time to pack your apps and migrate. What now? Well, the whole migration to the cloud process means:
- Inventory – check exactly what you have and what you are using. You could have apps that are not used, thus no transition needed.
- Analyze and Remediate – Are there potential changes that are needed, hard coded server names, analyze what tweaks are needed
- Transitional – how do I lift and shift this onto another system
- Cloud Endpoint – manage the server side, fixes, security, the client focuses on the app itself
Number one: INVENTORY. What you would need to do at this stage is sit down with your team and count the applications that you have, and also see exactly if they are still used and by whom.
Number two: ANALYZE and REMEDIATE. This step means that you will have to check if changes are needed. This is the moment when you have to see if you have any hard coded server names for instance which might prove to be an issue. Once you have identified these issues, you will need to see with your development team and your migration partner how to solve them.
Three on the list comes TRANSITION. The big day. You have everything selected, you know which applications you want to move, everything is in order. You will need to see and talk with your provider about the downtime and also decide upon the perfect time to do the transition so that your business is not affected.
Last but certainly not least comes: CLOUD ENDPOINT. This is where all the magic happens so to say. Everything is set and in order and the actual migration from your servers to your provider’s happens. Now, the most important aspect that you need to clarify with your provider is downtime so you can notify your clients and make sure that this downtime will be as short as possible. Other than that, you should be careful when selecting the provider so that this step can be easy for you. Something in the lines of having your team just check the apps not the whole backstory. This side should be taken care of by your migration partner.
There are also some other questions that will need an answer:
- Do you want to migrate just 10 apps or bring thousands of apps into a SaaS inventory?
- Is there time to retire some of the apps? Maybe they are not GDPR ready?
- Can you rewrite some apps since there are better ways to do what they do?
- What are your critical apps?
Once you figure this stuff out, the whole migration process should run pretty smoothly, especially if you have a team of professionals in your corner.
You might want to use this opportunity to get rid of some applications that you don’t use anymore for instance. You might also decide that it would be better to re-platform some apps and consolidate in the cloud. Domino 10 with Node.js support can help you do that.
So, we would say that migration of Domino applications to the cloud is easier than it has ever been and it also offers you some interesting opportunities. As in all techie operations, having the right wingman (cloud provider) is the thing that can make the difference between failure and success.