BizCom Global can assist and manage migration projects:
Lift and shift—Moving applications or servers as-is to another platform. Often this takes the form of creating a virtual machine and moving it to a new server, cluster, data center, or cloud.
Refactor—Modifying applications or servers to better support the new environment. This is most common when moving to the cloud and you need to get better efficiency from the new technologies.
Re-platform— Changing part of the application stack without changing the core architecture itself.
Rebuild—Rewriting the application with a full plan to leverage new platform capabilities.
Replace—Retiring the application and replacing it with a new application. Usually, this is a “data only” move to the new applications.
Whether it’s a “simple” email migration or a complex change of CRM systems many aspects are similar. It is important to note that even simple migrations often are more complex than most companies realize.
- Data, system, and application migrations come in all sizes and no two are built d the same.
- But they all require planning – some more, some less.
- The first conversation should be about risk. If you skip any core planning steps you risk chasing irrelevant details, wasting resources and money.
- If there are undocumented assets known only to select stakeholders,they are commonly overlooked in the discovery process.
- If you document too little, you risk migration failure.
- If you document too much, you risk budget and schedule overruns.
- Unless you perform a test migration, you don’t know that the launch will actually be successful.
- You risk reduced ROI unless you address team member skills, incentives and operational support requirements needed in your new environment. All migrations need to address:
- Understanding and agreeing to the scope
- Backup and fallback plans
- Platform – Changes
- People – making sure they know what is happening, when it is happening, and educating them about what is new
- Process – processes must change. They need to be thought through, documented, tested, and communicated. Are we moving what is or are we re-engineering it?
- Operations – how will it impact operations, will there be down time, what support will be required when we go live, what are the pitfalls, is this project dependent on outside factors, what in this project impacts other operations?
- Security – this vital area needs scrutiny and we will suggest options as we discuss the project.