DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/cloud-strategie -o yaml$ soultec get service/cloud-strategie -o json$ soultec get service/cloud-strategie -o toml$ soultec get service/cloud-strategie -o xml$ python3 cloud-strategie.pyPS> ./cloud-strategie.ps1$ go run cloud-strategie.go$ node cloud-strategie.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: cloud-strategie locale: en labels: group: consulting capability/cloud: 1.92 capability/strategy: 2.87 capability/migration: 2.82 vendor/microsoft: 2.61 annotations: source: src/content/services/en/cloud-strategie.md route: /en/services/cloud-strategie/ schema: /nerd/schema/services.json markdown: /en/services/cloud-strategie.mdspec: title: Cloud Strategy group: consulting audience: [enterprise, provider] order: 5 tags: [cloud, strategy, migration] vendors: [microsoft] summary: >- A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them. photoNeed: >- A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table stub: false draft: false sections: - heading:

Where it starts

body: | With an inventory. In the cloud assessment we record every application and service along with its dependencies and connections. That service catalogue is the basis for everything after it, and it is also the part almost nobody has in full. The dependencies are what matter. Moving one application is easy; separating it from the database three other systems also use is not. - heading:

The cloud readiness assessment

body: | We then check the applications for cloud fitness and assign each one of the **6 Rs**: - **Rehost** – lift and shift. The virtual servers move from your own private cloud onto the public cloud provider's infrastructure, and the application stays as it is. - **Replatform** – the architecture stays in principle, the foundation does not. An on-premises MySQL database becomes a managed database service, for example. - **Refactor** – the application is redesigned in its essentials and, where possible, run cloud-native. - **Repurchase** – the application is replaced outright by a SaaS product. - **Retire** – the application is switched off, because the service is delivered another way or is no longer needed at all. - **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or an operating system that runs nowhere else. Without this assignment a migration becomes a blanket move. That leads to running costs for applications you could have switched off, and to applications that run more expensively in the cloud than they did before. **Retire** is the underrated category. Every inventory turns up systems nobody needs any more that would otherwise have been migrated. - heading:

What comes out of it

body: | A future mode of operation per application, and therefore a migration you can plan and budget rather than start and see how far you get.status: corpus: 315 solutions: - {ref: solutions/microsoft/microsoft-azure, score: 0.42} - {ref: solutions/microsoft, score: 0.42} - {ref: solutions/hpe/hpe-morpheus/vm-essentials, score: 0.37} alsoLike: - {ref: experts/aldo-gwerder, score: 0.59} - {ref: services/cloud, score: 0.56} - {ref: experts/fabian-faessler, score: 0.55} experts: - {ref: experts/aldo-gwerder, score: 0.59} - {ref: experts/fabian-faessler, score: 0.55} - {ref: experts/matthias-grasmueck, score: 0.53} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "cloud-strategie", "locale": "en", "labels": { "group": "consulting", "capability/cloud": 1.92, "capability/strategy": 2.87, "capability/migration": 2.82, "vendor/microsoft": 2.61 }, "annotations": { "source": "src/content/services/en/cloud-strategie.md", "route": "/en/services/cloud-strategie/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/cloud-strategie.md" } }, "spec": { "title": "Cloud Strategy", "group": "consulting", "audience": [ "enterprise", "provider" ], "order": 5, "tags": [ "cloud", "strategy", "migration" ], "vendors": [ "microsoft" ], "summary": "A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": [ { "heading": "

Where it starts

", "body": "With an inventory. In the cloud assessment we record every application and service along\nwith its dependencies and connections. That service catalogue is the basis for everything\nafter it, and it is also the part almost nobody has in full.\n\nThe dependencies are what matter. Moving one application is easy; separating it from the\ndatabase three other systems also use is not." }, { "heading": "

The cloud readiness assessment

", "body": "We then check the applications for cloud fitness and assign each one of the **6 Rs**:\n\n- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto\n the public cloud provider's infrastructure, and the application stays as it is.\n- **Replatform** – the architecture stays in principle, the foundation does not. An\n on-premises MySQL database becomes a managed database service, for example.\n- **Refactor** – the application is redesigned in its essentials and, where possible, run\n cloud-native.\n- **Repurchase** – the application is replaced outright by a SaaS product.\n- **Retire** – the application is switched off, because the service is delivered another\n way or is no longer needed at all.\n- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or\n an operating system that runs nowhere else.\n\nWithout this assignment a migration becomes a blanket move. That leads to running costs for\napplications you could have switched off, and to applications that run more expensively in\nthe cloud than they did before.\n\n**Retire** is the underrated category. Every inventory turns up systems nobody needs any\nmore that would otherwise have been migrated." }, { "heading": "

What comes out of it

", "body": "A future mode of operation per application, and therefore a migration you can plan and\nbudget rather than start and see how far you get." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "0.42" }, { "ref": "solutions/microsoft", "score": "0.42" }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.37" } ], "alsoLike": [ { "ref": "experts/aldo-gwerder", "score": "0.59" }, { "ref": "services/cloud", "score": "0.56" }, { "ref": "experts/fabian-faessler", "score": "0.55" } ], "experts": [ { "ref": "experts/aldo-gwerder", "score": "0.59" }, { "ref": "experts/fabian-faessler", "score": "0.55" }, { "ref": "experts/matthias-grasmueck", "score": "0.53" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "cloud-strategie"locale = "en"[metadata.labels]group = "consulting""capability/cloud" = 1.92"capability/strategy" = 2.87"capability/migration" = 2.82"vendor/microsoft" = 2.61[metadata.annotations]source = "src/content/services/en/cloud-strategie.md"route = "/en/services/cloud-strategie/"schema = "/nerd/schema/services.json"markdown = "/en/services/cloud-strategie.md"[spec]title = "Cloud Strategy"group = "consulting"audience = ["enterprise", "provider"]order = 5tags = ["cloud", "strategy", "migration"]vendors = ["microsoft"]summary = "A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them."photoNeed = "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table"stub = falsedraft = false[[spec.sections]]heading = "

Where it starts

"body = '''With an inventory. In the cloud assessment we record every application and service alongwith its dependencies and connections. That service catalogue is the basis for everythingafter it, and it is also the part almost nobody has in full.The dependencies are what matter. Moving one application is easy; separating it from thedatabase three other systems also use is not.'''[[spec.sections]]heading = "

The cloud readiness assessment

"body = '''We then check the applications for cloud fitness and assign each one of the **6 Rs**:- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto the public cloud provider's infrastructure, and the application stays as it is.- **Replatform** – the architecture stays in principle, the foundation does not. An on-premises MySQL database becomes a managed database service, for example.- **Refactor** – the application is redesigned in its essentials and, where possible, run cloud-native.- **Repurchase** – the application is replaced outright by a SaaS product.- **Retire** – the application is switched off, because the service is delivered another way or is no longer needed at all.- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or an operating system that runs nowhere else.Without this assignment a migration becomes a blanket move. That leads to running costs forapplications you could have switched off, and to applications that run more expensively inthe cloud than they did before.**Retire** is the underrated category. Every inventory turns up systems nobody needs anymore that would otherwise have been migrated.'''[[spec.sections]]heading = "

What comes out of it

"body = '''A future mode of operation per application, and therefore a migration you can plan andbudget rather than start and see how far you get.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/microsoft/microsoft-azure"score = "0.42"[[status.solutions]]ref = "solutions/microsoft"score = "0.42"[[status.solutions]]ref = "solutions/hpe/hpe-morpheus/vm-essentials"score = "0.37"[[status.alsoLike]]ref = "experts/aldo-gwerder"score = "0.59"[[status.alsoLike]]ref = "services/cloud"score = "0.56"[[status.alsoLike]]ref = "experts/fabian-faessler"score = "0.55"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.59"[[status.experts]]ref = "experts/fabian-faessler"score = "0.55"[[status.experts]]ref = "experts/matthias-grasmueck"score = "0.53"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>cloud-strategie</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/cloud">1.92</entry> <entry key="capability/strategy">2.87</entry> <entry key="capability/migration">2.82</entry> <entry key="vendor/microsoft">2.61</entry> </labels> <annotations> <source>src/content/services/en/cloud-strategie.md</source> <route>/en/services/cloud-strategie/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/cloud-strategie.md</markdown> </annotations> </metadata> <spec> <title>Cloud Strategy</title> <group>consulting</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>5</order> <tags> <item>cloud</item> <item>strategy</item> <item>migration</item> </tags> <vendors> <item>microsoft</item> </vendors> <summary>A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.</summary> <photoNeed>A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

Where it starts

</heading> <body>With an inventory. In the cloud assessment we record every application and service alongwith its dependencies and connections. That service catalogue is the basis for everythingafter it, and it is also the part almost nobody has in full.The dependencies are what matter. Moving one application is easy; separating it from thedatabase three other systems also use is not. </body> </section> <section> <heading>

The cloud readiness assessment

</heading> <body>We then check the applications for cloud fitness and assign each one of the **6 Rs**:- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto the public cloud provider's infrastructure, and the application stays as it is.- **Replatform** – the architecture stays in principle, the foundation does not. An on-premises MySQL database becomes a managed database service, for example.- **Refactor** – the application is redesigned in its essentials and, where possible, run cloud-native.- **Repurchase** – the application is replaced outright by a SaaS product.- **Retire** – the application is switched off, because the service is delivered another way or is no longer needed at all.- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or an operating system that runs nowhere else.Without this assignment a migration becomes a blanket move. That leads to running costs forapplications you could have switched off, and to applications that run more expensively inthe cloud than they did before.**Retire** is the underrated category. Every inventory turns up systems nobody needs anymore that would otherwise have been migrated. </body> </section> <section> <heading>

What comes out of it

</heading> <body>A future mode of operation per application, and therefore a migration you can plan andbudget rather than start and see how far you get. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/microsoft/microsoft-azure</ref> <score>0.42</score> </item> <item> <ref>solutions/microsoft</ref> <score>0.42</score> </item> <item> <ref>solutions/hpe/hpe-morpheus/vm-essentials</ref> <score>0.37</score> </item> </solutions> <alsoLike> <item> <ref>experts/aldo-gwerder</ref> <score>0.59</score> </item> <item> <ref>services/cloud</ref> <score>0.56</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.55</score> </item> </alsoLike> <experts> <item> <ref>experts/aldo-gwerder</ref> <score>0.59</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.55</score> </item> <item> <ref>experts/matthias-grasmueck</ref> <score>0.53</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "cloud-strategie", "locale": "en", "labels": { "group": "consulting", "capability/cloud": 1.92, "capability/strategy": 2.87, "capability/migration": 2.82, "vendor/microsoft": 2.61, }, "annotations": { "source": "src/content/services/en/cloud-strategie.md", "route": "/en/services/cloud-strategie/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/cloud-strategie.md", }, }, "spec": { "title": "Cloud Strategy", "group": "consulting", "audience": ["enterprise", "provider"], "order": 5, "tags": ["cloud", "strategy", "migration"], "vendors": ["microsoft"], "summary": "A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": False, "draft": False, "sections": [ { "heading": "

Where it starts

", "body": ( "With an inventory. In the cloud assessment we record every application and service along\n" "with its dependencies and connections. That service catalogue is the basis for everything\n" "after it, and it is also the part almost nobody has in full.\n" "\n" "The dependencies are what matter. Moving one application is easy; separating it from the\n" "database three other systems also use is not." ), }, { "heading": "

The cloud readiness assessment

", "body": ( "We then check the applications for cloud fitness and assign each one of the **6 Rs**:\n" "\n" "- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto\n" " the public cloud provider's infrastructure, and the application stays as it is.\n" "- **Replatform** – the architecture stays in principle, the foundation does not. An\n" " on-premises MySQL database becomes a managed database service, for example.\n" "- **Refactor** – the application is redesigned in its essentials and, where possible, run\n" " cloud-native.\n" "- **Repurchase** – the application is replaced outright by a SaaS product.\n" "- **Retire** – the application is switched off, because the service is delivered another\n" " way or is no longer needed at all.\n" "- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or\n" " an operating system that runs nowhere else.\n" "\n" "Without this assignment a migration becomes a blanket move. That leads to running costs for\n" "applications you could have switched off, and to applications that run more expensively in\n" "the cloud than they did before.\n" "\n" "**Retire** is the underrated category. Every inventory turns up systems nobody needs any\n" "more that would otherwise have been migrated." ), }, { "heading": "

What comes out of it

", "body": ( "A future mode of operation per application, and therefore a migration you can plan and\n" "budget rather than start and see how far you get." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "0.42", }, { "ref": "solutions/microsoft", "score": "0.42", }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.37", }, ], "alsoLike": [ { "ref": "experts/aldo-gwerder", "score": "0.59", }, { "ref": "services/cloud", "score": "0.56", }, { "ref": "experts/fabian-faessler", "score": "0.55", }, ], "experts": [ { "ref": "experts/aldo-gwerder", "score": "0.59", }, { "ref": "experts/fabian-faessler", "score": "0.55", }, { "ref": "experts/matthias-grasmueck", "score": "0.53", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'cloud-strategie' locale = 'en' labels = [ordered]@{ group = 'consulting' 'capability/cloud' = 1.92 'capability/strategy' = 2.87 'capability/migration' = 2.82 'vendor/microsoft' = 2.61 } annotations = [ordered]@{ source = 'src/content/services/en/cloud-strategie.md' route = '/en/services/cloud-strategie/' schema = '/nerd/schema/services.json' markdown = '/en/services/cloud-strategie.md' } } spec = [ordered]@{ title = 'Cloud Strategy' group = 'consulting' audience = @('enterprise', 'provider') order = 5 tags = @('cloud', 'strategy', 'migration') vendors = @('microsoft') summary = 'A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.' photoNeed = 'A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table' stub = $false draft = $false sections = @( [ordered]@{ heading = '

Where it starts

' body = @'With an inventory. In the cloud assessment we record every application and service alongwith its dependencies and connections. That service catalogue is the basis for everythingafter it, and it is also the part almost nobody has in full.The dependencies are what matter. Moving one application is easy; separating it from thedatabase three other systems also use is not.'@ } [ordered]@{ heading = '

The cloud readiness assessment

' body = @'We then check the applications for cloud fitness and assign each one of the **6 Rs**:- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto the public cloud provider's infrastructure, and the application stays as it is.- **Replatform** – the architecture stays in principle, the foundation does not. An on-premises MySQL database becomes a managed database service, for example.- **Refactor** – the application is redesigned in its essentials and, where possible, run cloud-native.- **Repurchase** – the application is replaced outright by a SaaS product.- **Retire** – the application is switched off, because the service is delivered another way or is no longer needed at all.- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or an operating system that runs nowhere else.Without this assignment a migration becomes a blanket move. That leads to running costs forapplications you could have switched off, and to applications that run more expensively inthe cloud than they did before.**Retire** is the underrated category. Every inventory turns up systems nobody needs anymore that would otherwise have been migrated.'@ } [ordered]@{ heading = '

What comes out of it

' body = @'A future mode of operation per application, and therefore a migration you can plan andbudget rather than start and see how far you get.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/microsoft/microsoft-azure' score = '0.42' } [ordered]@{ ref = 'solutions/microsoft' score = '0.42' } [ordered]@{ ref = 'solutions/hpe/hpe-morpheus/vm-essentials' score = '0.37' } ) alsoLike = @( [ordered]@{ ref = 'experts/aldo-gwerder' score = '0.59' } [ordered]@{ ref = 'services/cloud' score = '0.56' } [ordered]@{ ref = 'experts/fabian-faessler' score = '0.55' } ) experts = @( [ordered]@{ ref = 'experts/aldo-gwerder' score = '0.59' } [ordered]@{ ref = 'experts/fabian-faessler' score = '0.55' } [ordered]@{ ref = 'experts/matthias-grasmueck' score = '0.53' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "cloud-strategie", "locale": "en", "labels": map[string]any{ "group": "consulting", "capability/cloud": 1.92, "capability/strategy": 2.87, "capability/migration": 2.82, "vendor/microsoft": 2.61, }, "annotations": map[string]any{ "source": "src/content/services/en/cloud-strategie.md", "route": "/en/services/cloud-strategie/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/cloud-strategie.md", }, }, "spec": map[string]any{ "title": "Cloud Strategy", "group": "consulting", "audience": []any{"enterprise", "provider"}, "order": 5, "tags": []any{"cloud", "strategy", "migration"}, "vendors": []any{"microsoft"}, "summary": "A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

Where it starts

", "body": "With an inventory. In the cloud assessment we record every application and service along\n" + "with its dependencies and connections. That service catalogue is the basis for everything\n" + "after it, and it is also the part almost nobody has in full.\n" + "\n" + "The dependencies are what matter. Moving one application is easy; separating it from the\n" + "database three other systems also use is not.", }, map[string]any{ "heading": "

The cloud readiness assessment

", "body": "We then check the applications for cloud fitness and assign each one of the **6 Rs**:\n" + "\n" + "- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto\n" + " the public cloud provider's infrastructure, and the application stays as it is.\n" + "- **Replatform** – the architecture stays in principle, the foundation does not. An\n" + " on-premises MySQL database becomes a managed database service, for example.\n" + "- **Refactor** – the application is redesigned in its essentials and, where possible, run\n" + " cloud-native.\n" + "- **Repurchase** – the application is replaced outright by a SaaS product.\n" + "- **Retire** – the application is switched off, because the service is delivered another\n" + " way or is no longer needed at all.\n" + "- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or\n" + " an operating system that runs nowhere else.\n" + "\n" + "Without this assignment a migration becomes a blanket move. That leads to running costs for\n" + "applications you could have switched off, and to applications that run more expensively in\n" + "the cloud than they did before.\n" + "\n" + "**Retire** is the underrated category. Every inventory turns up systems nobody needs any\n" + "more that would otherwise have been migrated.", }, map[string]any{ "heading": "

What comes out of it

", "body": "A future mode of operation per application, and therefore a migration you can plan and\n" + "budget rather than start and see how far you get.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/microsoft/microsoft-azure", "score": "0.42", }, map[string]any{ "ref": "solutions/microsoft", "score": "0.42", }, map[string]any{ "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.37", }, }, "alsoLike": []any{ map[string]any{ "ref": "experts/aldo-gwerder", "score": "0.59", }, map[string]any{ "ref": "services/cloud", "score": "0.56", }, map[string]any{ "ref": "experts/fabian-faessler", "score": "0.55", }, }, "experts": []any{ map[string]any{ "ref": "experts/aldo-gwerder", "score": "0.59", }, map[string]any{ "ref": "experts/fabian-faessler", "score": "0.55", }, map[string]any{ "ref": "experts/matthias-grasmueck", "score": "0.53", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "cloud-strategie", locale: "en", labels: { group: "consulting", "capability/cloud": 1.92, "capability/strategy": 2.87, "capability/migration": 2.82, "vendor/microsoft": 2.61, }, annotations: { source: "src/content/services/en/cloud-strategie.md", route: "/en/services/cloud-strategie/", schema: "/nerd/schema/services.json", markdown: "/en/services/cloud-strategie.md", }, }, spec: { title: "Cloud Strategy", group: "consulting", audience: ["enterprise", "provider"], order: 5, tags: ["cloud", "strategy", "migration"], vendors: ["microsoft"], summary: "A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.", photoNeed: "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", stub: false, draft: false, sections: [ { heading: "

Where it starts

", body: "With an inventory. In the cloud assessment we record every application and service along\n" + "with its dependencies and connections. That service catalogue is the basis for everything\n" + "after it, and it is also the part almost nobody has in full.\n" + "\n" + "The dependencies are what matter. Moving one application is easy; separating it from the\n" + "database three other systems also use is not.", }, { heading: "

The cloud readiness assessment

", body: "We then check the applications for cloud fitness and assign each one of the **6 Rs**:\n" + "\n" + "- **Rehost** – lift and shift. The virtual servers move from your own private cloud onto\n" + " the public cloud provider's infrastructure, and the application stays as it is.\n" + "- **Replatform** – the architecture stays in principle, the foundation does not. An\n" + " on-premises MySQL database becomes a managed database service, for example.\n" + "- **Refactor** – the application is redesigned in its essentials and, where possible, run\n" + " cloud-native.\n" + "- **Repurchase** – the application is replaced outright by a SaaS product.\n" + "- **Retire** – the application is switched off, because the service is delivered another\n" + " way or is no longer needed at all.\n" + "- **Retain** – nothing changes. Reasons are latency requirements, legacy applications, or\n" + " an operating system that runs nowhere else.\n" + "\n" + "Without this assignment a migration becomes a blanket move. That leads to running costs for\n" + "applications you could have switched off, and to applications that run more expensively in\n" + "the cloud than they did before.\n" + "\n" + "**Retire** is the underrated category. Every inventory turns up systems nobody needs any\n" + "more that would otherwise have been migrated.", }, { heading: "

What comes out of it

", body: "A future mode of operation per application, and therefore a migration you can plan and\n" + "budget rather than start and see how far you get.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/microsoft/microsoft-azure", score: "0.42", }, { ref: "solutions/microsoft", score: "0.42", }, { ref: "solutions/hpe/hpe-morpheus/vm-essentials", score: "0.37", }, ], alsoLike: [ { ref: "experts/aldo-gwerder", score: "0.59", }, { ref: "services/cloud", score: "0.56", }, { ref: "experts/fabian-faessler", score: "0.55", }, ], experts: [ { ref: "experts/aldo-gwerder", score: "0.59", }, { ref: "experts/fabian-faessler", score: "0.55", }, { ref: "experts/matthias-grasmueck", score: "0.53", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 81 lines · YAML · validated at build# 102 lines · JSON · validated at build# 114 lines · TOML · validated at build# 133 lines · XML · validated at build# 130 lines · Python · read back at build, equals the JSON record# 127 lines · PowerShell · read back at build, equals the JSON record# 136 lines · Go · read back at build, equals the JSON record# 121 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/cloud-strategie.md

Service · consulting

Cloud Strategy

A cloud assessment before the migration. Every application gets one of the 6 Rs, and rehost is rarely the right answer for all of them.

Topics Cloud 1.92 Strategy 2.87 Migration 2.82

Vendors Microsoft 2.61

03Solutions

03Capabilities

01Vendors

315Corpus

photograph wantedA working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table

Where it starts

With an inventory. In the cloud assessment we record every application and service along with its dependencies and connections. That service catalogue is the basis for everything after it, and it is also the part almost nobody has in full.

The dependencies are what matter. Moving one application is easy; separating it from the database three other systems also use is not.

The cloud readiness assessment

We then check the applications for cloud fitness and assign each one of the 6 Rs:

Rehost – lift and shift. The virtual servers move from your own private cloud onto the public cloud provider’s infrastructure, and the application stays as it is.
Replatform – the architecture stays in principle, the foundation does not. An on-premises MySQL database becomes a managed database service, for example.
Refactor – the application is redesigned in its essentials and, where possible, run cloud-native.
Repurchase – the application is replaced outright by a SaaS product.
Retire – the application is switched off, because the service is delivered another way or is no longer needed at all.
Retain – nothing changes. Reasons are latency requirements, legacy applications, or an operating system that runs nowhere else.

Without this assignment a migration becomes a blanket move. That leads to running costs for applications you could have switched off, and to applications that run more expensively in the cloud than they did before.

Retire is the underrated category. Every inventory turns up systems nobody needs any more that would otherwise have been migrated.