Migrating to AWS in Less than 9 Days

Case Study
Migrating to AWS in Less than 9 Days
Flamingo Software automated onboarding with CloudVelox
Miami based Flamingo Software LLC provides
administrative services and software support to
insurance and financial services firms.
In 2013 the company looked into migrating some of
the virtual servers to
Amazon AWS, to boost
availability and make it
"It was a
easier for remote IT workers
relatively
to manage critical systems.
painless
“In 2013 we evaluated a
variety of cloud migration
process."
tools,” commented Flamingo
Software’s IT Manager
Christophe Loisey. ”They were
too hard to use, very hands-on and not reliable,” he
lamented. “They had a long way to go when it came to
Flamingo
Software
Data Center
OHC™ Platform
Physical
Server
2008
Virtual
Server
2008 R2
Secure
Network
Extension
SQL
Server
Virtual
Server
2008 R2
Virtual
Server
2008 R2
Existing Environment:
• Limited Bandwidth - 15 Mb/s available
(of 20 Mb/s)
• Live Synchronization and Migration
• Tight time requirements
(9 Days, start to finish)
being user friendly. So we postponed the migration.”
Early in 2014, the company decided to move all its
production servers to the cloud so they looked again
into migrating tools. At that time, they heard about
CloudVelox as well as other solutions. After evaluating
each choices, they decided to
use CloudVelox. “Over the
course of two weekends, we
accomplished with CloudVelox
what we thought was
impossible: we migrated our
entire environment of virtual
workloads as well as a physical
server into AWS.”
OHC™ Platform
EC
Server
2008
EC2
Server
2008 R2
SQL
Server
EC2
Server
2008 R2
EC2
Server
2008 R2
The Case for AWS
Flamingo Software has a small,
dedicated IT team responsible
for critical online systems used
by employees and customers.
The public cloud was a natural
fit; it allowed the team to have
24/7 access from anywhere
with internet access, which was
Flamingo Software's 9 day Cloud Migration.
1
CloudVelox Case Study: Flamingo Sofware Migration Into AWS
Copyright © 2014 CloudVelox Inc. All rights reserved. www.cloudvelox.com
Case Study: Flamingo Software Migration Into AWS
a substantial productivity boost. It also
answers the concerns of having production
servers hosted in a hurricane area.
“Once we migrated to Amazon AWS it became
much easier for us to adequately support the
company,” Loisey shared. “We were also able
to enhance the availability of our systems to
an extent that we couldn’t have with our
premise-bound apps. Getting our workloads
into AWS helped us on many fronts.”
Discovery
Provisioning
Service Initiation
1
3
5
2
4
Blueprinting
Synchronization
The Case for CloudVelox
Traditional cloud migration tools couldn’t help
Figure two: The OHC™ 5 Step Automated Process.
the Flamingo Software IT team to migrate
their mixed (physical and virtual) environment
into AWS. They required too much support.
The CloudVelox One Hybrid Cloud™ platform automated
critical discovery, blueprinting and deployment
processes within a very easy to use GUI driven by point
and click menus. What would normally have taken
Migration Challenges
• Mixed Environment (physical and virtual
servers)
• Cloud Migration Tools Required Heavy
Customization
"Over two weekends
we accomplished with
CloudVelox what we thought
was impossible..."
• Limited Bandwidth – 15 Mb/s
CloudVelox Payoff
weeks or months was accomplished over the course of
two weekends.
The CloudVelox professional service team was not only
responsive but highly qualified to assist with our
deployment. “We weren’t left waiting for answers or advice,”
Loisey continued. “It was a relatively painless process.”
• Live Synchronization and Migration
• 80%+ of Critical Processes Automated
• Agility: Nine Days from Start to Finish
CloudVelox, 2350 Mission College Blvd., Ste. 1250, Santa Clara, CA 95054 • 408.841.4800 • www.cloudvelox.com
Copyright © 2014 CloudVelox Inc. All rights reserved. CloudVelox and One Hybrid Cloud, are trademarks of CloudVelox in the United States
and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.