CloudHound

Data residency is one of the first questions in every European migration. Customers want to know which country their discovery data is held in, and for many French customers the answer needs to be France 🌍 I'm pleased to announce that CloudHound now runs in Europe (Paris), our third European region alongside London and Frankfurt, and our seventeenth worldwide. Paris runs its own copy of the platform and its own database, so a French customer's discovery and assessment data is held in France. Partners can now pick the right home for each customer: - Europe (London) for UK estates - Europe (Frankfurt) for German and central European estates - Europe (Paris) for French estates Migration works the same way: replicas are written straight into the customer's own cloud account, in whichever region they choose, and our servers never carry the disks. The platform is also fully translated into French, so the customer's operations team can run every project in their own language. For public sector, health and financial estates in Europe, that keeps data in-country from the first discovery scan through to a complete migration, using the platform with the best operating system compatibility, the fastest migrations, and the shortest cutover times available for AWS. Three regions across Europe, for migration assessment, planning, and execution 💫 cloudhound.io

At CloudHound we are going for ultra legacy. That means that every operating system that was ever supported on EC2 we will reliably replicate and convert for you and your migration customers. But what about operating systems that were never supported? How far back can you actually go? It turns out quite far indeed ⏳ The earliest versions of operating systems that were ever supported for migration into EC2 were: Debian 6 - Squeeze (2011) RHEL 5 - Tikanga (2007) Ubuntu 12.04 - Precise Pangolin (2012) SUSE 11 SP1 (2010) FreeBSD 8.2 (2011) - EC2 only, never for migration EC2 was released to the public in 2008, but it turns out you can go much further back than that. We can now reliably migrate ultra legacy workloads, going back 26 years, including: Debian 2.2 - Potato (2000) - 26 yrs old RHEL 2.1 - Pensacola (2002) - 24 yrs old Ubuntu 4.10 - Warty Warthog (2004) - 22 yrs old SUSE 8 (2002) - 24 yrs old FreeBSD 3.5 (2000) - 26 yrs old In addition to Windows 2003, 32-bit and 64-bit editions. Enterprises still run these, and it's for workloads they can't reliably upgrade. Should that be a blocker for their migration? No, it shouldn't be. You should be able to migrate and park them just the same. If you're facing legacy, or ultra legacy workloads - look to CloudHound 💫 cloudhound.io

¿Trabajas en migraciones a AWS? それとも日本語で? 🌍 The entire CloudHound platform is now translated into 14 languages: English, German, Spanish, French, Indonesian, Brazilian Portuguese, Vietnamese, Hebrew, Arabic, Hindi, Japanese, Korean, Simplified Chinese and Traditional Chinese. That covers the whole platform: - Every screen, discovery, costing, wave planning, replication and cutover - All of our extensive documentation - Error messages, launch steps and health findings - The explanations behind every readiness and migration result - All chats and artifacts from our expert AI console, ask ch - Even console commands, with every installer in the user's own language Hebrew and Arabic read right to left across the entire interface, and every user can chose their own language. With 89 partners across 29 countries, our partners are not all working in English. A delivery lead in São Paulo, an architect in Seoul and a customer's operations team in Dubai can now work in the same portfolio, each in their own language, with data kept local in any of our 16 global regions. One Engine, fourteen languages - look to CloudHound 💫 cloudhound.io

Two days ago I posted about migrating a 5.1 TiB SQL Server to AWS in 13 minutes. But what about your average enterprise server? So we timed one. A 240 GiB Ubuntu server running in Hetzner, migrating to AWS Frankfurt, measured from the moment the copy was started until the server was confirmed running and accessible in EC2. We ran it twice, once with AWS native replication and once with CloudHound. AWS native replication took 3 hours 56 minutes. CloudHound took 2 minutes ⚡ The conversation with your customer is now no longer "how long will it take", it's "when would you like it running". It's not "can we replicate this", it's "we can handle that". CloudHound discovers, costs, plans, replicates, converts and launches in one engine, with support for over 100 operating system variants, back to RedHat 4 and Windows 2003, and is free for MAP partners. If you are running cloud migrations into AWS or OCI, please get in touch. cloudhound.io

Do you have legacy operating systems you need to migrate? 🤔 We checked 40 organisations, and 65% have operating systems that AWS native replication no longer supports. Not us however, we are going for ultra legacy. Our migration engine will convert and boot 99% of the servers CloudHound has ever discovered into EC2. On Windows that goes from 2003, for Linux it's RHEL 4, Oracle Linux 4, SLES 11, Debian 6 and Ubuntu 12.04, covering 17 distributions. We even support FreeBSD, something no other tool does. Have you got an Azure to AWS migration? We kernel swap Azure Ubuntu variants to the AWS kernel in 2 seconds, saving you 5 hours per VM. Azure Linux? We can convert that too, as we host a repository for Azure Linux AWS network drivers. If a customer hasn't upgraded a server in 20 years, there's probably a reason. And if it can't be migrated to AWS, it might delay the whole project. It's no longer a problem. If your operating system has ever run on EC2, we will support it. If you are mid migration and are facing issues with legacy estates, get in touch 💫 cloudhound.io

We've found data residency to be an important part of cloud migrations. Customers want to know where their discovery data is stored, who can reach it, and whether it ever leaves their region 🌍 That's why I'm pleased to announce that CloudHound now runs in four more AWS regions, bringing us to sixteen: - Africa (Cape Town) - South America (São Paulo) - Mexico (Central) - Israel (Tel Aviv) Each region is a full CloudHound deployment, so a customer's assessment data is collected, processed and stored in their home region. When it's time to migrate, our migration engine streams data directly from their data centre into their AWS or OCI account, never through us. For partners delivering MAP across Africa, Latin America and the Middle East, this makes assessments and migrations easier. Customers in government, healthcare, finance and other regulated industries can now be assessed and migrated with their data held in-region, using the engine with the fastest known migration speeds and best compatibility in the industry. Sixteen regions across the Americas, Europe, the Middle East, Africa and Asia Pacific 💫 cloudhound.io