5 Cloud Migration Mistakes to Avoid
•Download as PPTX, PDF•
0 likes•346 views
This document summarizes key lessons learned from cloud migration experiences that should be avoided. It discusses developing realistic project scopes that allow time for discovery and testing. Managing timelines carefully by estimating data transfer times and allowing ample testing periods is important. Avoiding security risks requires reviewing firewalls, intrusion detection, and compliance. Thorough testing that runs the test plan at least three times is crucial. Finally, clear communication of roles, access, expectations for maintenance windows and cutovers is needed.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to 5 Cloud Migration Mistakes to Avoid
Similar to 5 Cloud Migration Mistakes to Avoid (20)
More from Hostway|HOSTING
More from Hostway|HOSTING (20)
Recently uploaded
Recently uploaded (20)
5 Cloud Migration Mistakes to Avoid
- 1. 1 5 Cloud Migration Experiences Not to Be Repeated
- 2. • This webinar is being recorded and an on-demand version will be available at the same URL at the conclusion of the webinar • Please submit questions via the button on the upper left of the viewer • If we don’t get to your question during the webinar, we will follow up with you via email • Download related resources via the “Attachments” button above the viewing panel • On Twitter? Join the conversation: #cloudmigrations @HOSTINGdotcom 2 Housekeeping
- 3. 3 Our speaker today: Kellen Amobi Program Manager, HOSTING
- 4. 4 Migrations to the Cloud • Costly • High risk • Time consuming
- 5. • Developing realistic project scopes • Managing timelines • Avoiding security risks • Testing, Testing, Testing • Communicating expectations 5 Mitigating Risk and Avoiding Costly Mistakes
- 7. • Allow time for discovery • Create keep/migrate/remove strategy for each component • Break into phases • What does success look like? 7 Developing realistic project scope
- 8. Schedule 8
- 9. 9 Managing Timelines • Test network speeds to estimate data transfer • Allow plenty of time for testing/validation
- 11. 11 Avoiding Security Risks Eighty-six percent of all websites have at least one serious vulnerability, and most of the time, they contain more than one, according to WhiteHat Security's “2015 Website Security Statistics Report.”
- 12. • Review firewall policy • Add an intrusion detection system, log manager and/or web application firewall • Review compliance requirements 12 Avoiding Security Risks
- 13. Testing 13
- 14. • Allow plenty of time for testing and validation • Client must establish success criteria • Run test plan at least 3 times – in current environment, in new environment before cutover, in new environment post-cutover 14 Testing, Testing, Testing
- 15. Communication 15
- 16. • Discuss roles and responsibilities • Who will create/execute test plan? • Provide access and insight into the original environment • Approval for maintenance windows • Communicate with end users for changes/outages 16 Communicating Expectations
- 17. • Cutover expectations • specific date/time • length of window • allowable downtime • These factors can change the approach for how to migrate the data 17 Communicating Expectations
- 18. • Build in a discovery phase • Allow lots of time for testing • Start with a secure environment • Test 3x • Share expectations 18 Key Takeaways
- 19. 19 Q&A For more information about cloud migration by HOSTING, please contact our team at 888.894.4678.
Editor's Notes
- Migrations to the cloud can be expensive, require a lot of resources and involve a lot of risk. They aren’t something that the customer does frequently, so it may be difficult to draw on experience.
- Today we’re going to talk about the top 5 mistakes that companies make during a migration to the cloud and how you can avoid them. We’ll take a look at developing realistic project scopes, managing timelines, …
- It’s very important to start out with a realistic project scope. Discovery/information sharing is key to developing a realistic migration plan -so how do you define the scope so that you have a successful migration? -You may be faced with a lot of unknowns in the source environment, so you should build in a discovery phase. --Migrations tend to uncover a lot of stuff that the company may have been overlooking or neglecting for some time -You should also define what success looks like – is it to have everything functioning exactly the way it did in the original environment, is the focus on just getting the critical application up and running while they worry about the other pieces later or are they looking for better performance in the new environment?
- -Data transfers can be extremely variable. From my experience, it usually takes longer than we expect, so run some data transfer tests around the same time as you will for the final cutover to get an accurate time estimate. -we’ll go over testing and validation a little later in the presentation. We want to allow for time to test/validate and resolve any issues that come out of it.
- We all know that security is important, but there is a great opportunity while doing a migration to “start fresh” and make sure your new Cloud environment is as secure as possible.
- Don't copy over the same security vulnerabilities - take this time to review firewall policy, add an IDS, log manager or web application firewall.
- The number one mistake we see with migrations to the Cloud is the client assumes that they will have very little involvement and the migration team assumes that the client knows that they will need to be very involved on some parts of the project.
- Be sure to ask/share this information up front because it could affect the strategy for the migrating the data. I’ve participated in projects where we were close to the end and the technician migrating says “the database is going to be offline for 10 hours by my calculations. Are we ready to move forward?” and the answer is “we can’t afford to be offline for that long.”
- The number one mistake we see with migrations to the Cloud is the client assumes that they will have very little involvement and the migration team assumes that the client knows that they will need to be very involved on some parts of the project.