<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Migration on Top AI Skills</title><link>https://topaiskills.com/tags/cloud-migration/</link><description>Recent content in Cloud Migration on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/cloud-migration/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Planner Skills: infra-planner vs cloud-migrate</title><link>https://topaiskills.com/tutorials/comparison/azure-planner-skills-comparison/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/comparison/azure-planner-skills-comparison/</guid><description>&lt;p&gt;Microsoft&amp;rsquo;s azure-skills pack carries two planning skills, and people install the wrong one constantly. azure-enterprise-infra-planner architects landing zones; azure-cloud-migrate ports existing workloads from AWS, GCP, and K8s. I read both SKILL.md files in full (planner v1.4.1, migrator v1.3.2, both MIT), worked through the planner&amp;rsquo;s phase-gate workflow and the migrator&amp;rsquo;s 37-file reference tree, then scraped the skills.sh leaderboard on 2026-09-04: infra-planner sits at #121 with 398.4K installs, cloud-migrate at #68 with 495.6K.&lt;/p&gt;</description></item><item><title>azure-upgrade: Assess, Then Migrate Azure Plans and SKUs</title><link>https://topaiskills.com/skills/automation/azure-upgrade/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-upgrade/</guid><description>&lt;p&gt;Most Azure upgrades get attempted as a chain of CLI commands typed from memory. Microsoft&amp;rsquo;s azure-upgrade skill refuses that pattern: it produces an assessment report before it changes anything, and it documents rollback before it executes. I read the current SKILL.md (v1.2.1, MIT), the workflow-details and global-rules files, plus the functions, Redis, and Java scenario references, then pulled install numbers off the skills.sh leaderboard on 2026-09-04.&lt;/p&gt;
&lt;h2 id="the-seven-step-flow-gates-every-upgrade"&gt;The Seven-Step Flow Gates Every Upgrade&lt;/h2&gt;
&lt;p&gt;The pipeline runs Identify → Assess → Pre-migrate → Upgrade → Validate → Ask User → hand off. No phase is skippable, and a failure inside any phase stops the run: log it in &lt;code&gt;upgrade-status.md&lt;/code&gt;, do not proceed, tell the user what broke, offer retry or rollback.&lt;/p&gt;</description></item><item><title>azure-cloud-migrate: Microsoft's 8-Scenario Migration Skill</title><link>https://topaiskills.com/skills/automation/azure-cloud-migrate/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-cloud-migrate/</guid><description>&lt;p&gt;Migrate a Lambda function to Azure and most agents start rewriting handler code from memory. Microsoft&amp;rsquo;s azure-cloud-migrate skill does the opposite: it demands an assessment report &lt;em&gt;before&lt;/em&gt; any code conversion, then routes you into one of eight scenario-specific guides. I read the current SKILL.md (v1.3.2, MIT) plus the full 37-file reference tree — three service families, per-runtime migration rules, and a progress-tracking convention — then pulled install numbers from the skills.sh leaderboard on 2026-09-02.&lt;/p&gt;</description></item></channel></rss>