Cloud Strategy

apiVersion: soultec.ch/v1kind: Servicemetadata: name: cloud-strategie locale: en labels: group: consulting capability/cloud: 1.94 capability/strategy: 3.54 capability/migration: 3.54 vendor/microsoft: 2.53 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 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, replatform, refactor, repurchase, retire, retain. That is the actual point of the exercise. Without it a migration becomes a blanket move, and a blanket move ends in running costs for applications you could have switched off, and applications running in the cloud more expensively 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: 267 solutions: - {ref: solutions/microsoft/microsoft-azure, score: 0.40} - {ref: solutions/microsoft, score: 0.40} - {ref: solutions/omnissa/citrix-takeout, score: 0.22} alsoLike: - {ref: services/cloud, score: 0.57} - {ref: services/digital-workplace, score: 0.52} - {ref: experts/aldo-gwerder, score: 0.39} experts: - {ref: experts/aldo-gwerder, score: 0.39} - {ref: experts/daniel-stadelmann, score: 0.39} - {ref: experts/fabian-faessler, score: 0.38}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "cloud-strategie", "locale": "en", "labels": { "group": "consulting", "capability/cloud": "1.94", "capability/strategy": "3.54", "capability/migration": "3.54", "vendor/microsoft": "2.53" }, "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", "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**:\nrehost, replatform, refactor, repurchase, retire, retain.\n\nThat is the actual point of the exercise. Without it a migration becomes a blanket move,\nand a blanket move ends in running costs for applications you could have switched off, and\napplications running in the cloud more expensively 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": 267, "solutions": [ { "ref": "solutions/microsoft/microsoft-azure", "score": "0.40" }, { "ref": "solutions/microsoft", "score": "0.40" }, { "ref": "solutions/omnissa/citrix-takeout", "score": "0.22" } ], "alsoLike": [ { "ref": "services/cloud", "score": "0.57" }, { "ref": "services/digital-workplace", "score": "0.52" }, { "ref": "experts/aldo-gwerder", "score": "0.39" } ], "experts": [ { "ref": "experts/aldo-gwerder", "score": "0.39" }, { "ref": "experts/daniel-stadelmann", "score": "0.39" }, { "ref": "experts/fabian-faessler", "score": "0.38" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "cloud-strategie"locale = "en"[metadata.labels]group = "consulting""capability/cloud" = "1.94""capability/strategy" = "3.54""capability/migration" = "3.54""vendor/microsoft" = "2.53"[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"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[[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.'''[[sections]]heading = "

The cloud readiness assessment

"body = '''We then check the applications for cloud fitness and assign each one of the **6 Rs**:rehost, replatform, refactor, repurchase, retire, retain.That is the actual point of the exercise. Without it a migration becomes a blanket move,and a blanket move ends in running costs for applications you could have switched off, andapplications running in the cloud more expensively than they did before.**Retire** is the underrated category. Every inventory turns up systems nobody needs anymore that would otherwise have been migrated.'''[[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 = 267[[status.solutions]]ref = "solutions/microsoft/microsoft-azure"score = "0.40"[[status.solutions]]ref = "solutions/microsoft"score = "0.40"[[status.solutions]]ref = "solutions/omnissa/citrix-takeout"score = "0.22"[[status.alsoLike]]ref = "services/cloud"score = "0.57"[[status.alsoLike]]ref = "services/digital-workplace"score = "0.52"[[status.alsoLike]]ref = "experts/aldo-gwerder"score = "0.39"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.39"[[status.experts]]ref = "experts/daniel-stadelmann"score = "0.39"[[status.experts]]ref = "experts/fabian-faessler"score = "0.38"

<?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.94</entry> <entry key="capability/strategy">3.54</entry> <entry key="capability/migration">3.54</entry> <entry key="vendor/microsoft">2.53</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> <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> </spec> <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, replatform, refactor, repurchase, retire, retain.That is the actual point of the exercise. Without it a migration becomes a blanket move,and a blanket move ends in running costs for applications you could have switched off, andapplications running in the cloud more expensively 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> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/microsoft/microsoft-azure</ref> <score>0.40</score> </item> <item> <ref>solutions/microsoft</ref> <score>0.40</score> </item> <item> <ref>solutions/omnissa/citrix-takeout</ref> <score>0.22</score> </item> </solutions> <alsoLike> <item> <ref>services/cloud</ref> <score>0.57</score> </item> <item> <ref>services/digital-workplace</ref> <score>0.52</score> </item> <item> <ref>experts/aldo-gwerder</ref> <score>0.39</score> </item> </alsoLike> <experts> <item> <ref>experts/aldo-gwerder</ref> <score>0.39</score> </item> <item> <ref>experts/daniel-stadelmann</ref> <score>0.39</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.38</score> </item> </experts> </status></manifest>

Where it starts

The cloud readiness assessment

What comes out of it

Where it starts

The cloud readiness assessment

What comes out of it

Where it starts

The cloud readiness assessment

What comes out of it

Where it starts

The cloud readiness assessment

What comes out of it

Where it starts

The cloud readiness assessment

What comes out of it

Experts for this

Aldo Gwerder

Daniel Stadelmann

Fabian Fässler

You might also like

Cloud

Digital Workplace

Aldo Gwerder