4 ways to move your custom legacy apps to the cloud
Elevate your technology and enterprise data strategy to Transform 2021.
Change comes in all shapes and sizes. We welcome some changes and others we hesitate. The pandemic has placed tremendous emphasis on the need to change business operations and many organizations have been placed in ‘do or die’ situations when it comes to going remotely, virtualizing workstations. work and, perhaps more importantly, deciding whether on-premises applications should stay, move to the cloud, or be replaced entirely.
Such decisions have been a long time coming. The on-premises IT footprint has shrunk over the past 10 years with the emergence of the cloud, highly customizable SaaS applications, and composable business principles. We no longer live in an office with a server room, and our feet are no longer tangled in large spools of thread under our desks. We are at home. We are mobile. And we are ushering in a new era of computing.
So it’s no longer a question of when to move to the cloud, but how. Here are four different approaches to consider:
Approach 1: lift and move
The fastest and easiest of the four approaches, lift and shift requires no code or architecture changes and is simply putting an application in the cloud using its current deployment architecture on new “hardware”. This popular option is available to businesses following the emergence of infrastructure as a service in public and private clouds.
For those looking to get around quickly, efficiently and inexpensively, it doesn’t get better than this. This may not always be the most optimal migration strategy, and there are certainly downsides to consider.
The biggest downside to this approach is the management of the long-term scalability and manageability of the application. Born in an on-premises environment, a legacy application is accustomed to (and sometimes designed for) a certain workload. Therefore, before you move it and move it to the cloud, you should first thoroughly test the performance and scalability, especially when you separate the users from the application or data by a WAN. Without proper testing, you’ll never know which drop of water will break the camel’s back, and you might find that an influx of customers, users, or even staff throws an app overboard and causes it to malfunction. . If it is just a mail server application or a time recording system, the damage may not be too severe, but if you have unsuccessfully lifted and moved your platform from selling in the cloud, your bottom line could suffer.
Approach 2: reconstruct / refactor
At the other end of the spectrum, we have the ability to rebuild or refactor your legacy applications. Refactoring is the process of moving the application to a public cloud and reorganizing it to take advantage of cloud native technologies, such as Platform as a Service. This requires significant code changes and is a long-term investment. Knowing that many custom legacy applications have links within the company, dependencies with other applications, and workflows to follow, it is essential that each relationship is updated so that there is no no downtime once in the cloud. This is the most sustainable approach to migrating an application; it will be scalable for any increase in demand or use, will be available remotely, and will continue to meet all business needs. By adhering to modern, cloud-native architecture best practices, you can ensure that your application will be scalable and compatible over the long term.
The main downside here is the cost associated with refactoring. This is a tedious process that essentially involves rebuilding the entire application in a new environment, with new technology and new code. This can mean outsourcing the task to migration specialists if your team is not equipped with the right skills. This can be a big project, but it will bring the application into a bearable and relatively scalable model.
Approach 3: Re-platform
Application reconfiguration is the middle ground between lift-and-shift and refactoring and usually involves making “easy” changes to the architecture of the application, for example by changing the way the application interacts. with its database to take advantage of serverless database cloud services. . Assuming the application is not too ‘chatty’ and works well when separated from its database over a WAN, moving the database level during a re-platform project might be. the best starting point.
When reconfiguring applications, you usually don’t change the client side, but the way it interacts with data may be different. To make sure nothing is drifting in the cloud, it’s important to closely monitor the app once it’s been re-platform. The main difference between this approach and refactoring / rebuilding is that it is faster and therefore is often the first step in the modernization journey of an application. You can’t capture everything in the re-platform process, and issues can arise on the fly. As long as you know this and have backup plans in place, this approach is very valuable and is a solid starting point if you decide to refactor later.
Approach 4: get rid of the app and buy a new one
The final approach is to get rid of your legacy app and buy a standard SaaS that you can customize. This is a delicate approach to prescribe and is only viable in certain situations. If you’re still hosting your mail server, then get rid of it and get Office 365 from Google Workspace. Likewise, any application that would be considered commonplace in the workplace, such as a CRM, HRM, or accounting solution, is also very likely to be replaced by a new SaaS product designed for the workplace. cloud. The times you would avoid this approach is when you have an app that has been heavily personalized and is not replicable with current market offerings.
If you decide to switch from a legacy app to a more modern SaaS app by exporting / importing data, the legacy app is almost always kept in read-only archive mode. This can provide staff with the information they need during the migration process, but they won’t have the functionality of the old app to change that information. This approach can be useful if you are looking to revamp your business, reduce technical debt, and take advantage of technology upgrades, but users may need training on the new application, and you should consider this in the migration process.
Find the right migration strategy for you
It is important to understand that every instance is unique and that while one approach may work well for an application, there is no universally “correct” way to go about the migration process. You can refactor one or two of your most business-critical applications, restructure a secondary platform, and lift and move a few minor ones.
However, one consideration that you should apply in your decision-making process is how these movements, or changes, will impact employee productivity. Making decisions like these in a C suite vacuum can lead to frustration on the front line when staff have to implement changes, learn new technology, or settle for a broken application that isn’t everything. quite suitable. As long as you consider your business needs, the urgency of the migration, and the business and operational impact it will have, you can’t go wrong in migrating to the cloud.
Vadim Vladimirskiy is co-founder and CEO of Nerdio.
VentureBeat’s mission is to be a digital public place for technical decision-makers to learn about transformative technology and conduct transactions. Our site provides essential information on data technologies and strategies to guide you in managing your organizations. We invite you to become a member of our community, to access:
- up-to-date information on the topics that interest you
- our newsletters
- Closed thought leader content and discounted access to our popular events, such as Transform 2021: Learn more
- networking features, and more
Become a member