---
title: "Provision an Application Landing Zone through Self-Service"
description: "Guide Application Owners from a published Configurator template through project ordering, Plan review, deployment, and handover to workload migration."
scfTrail:
  tags: ["design-and-mobilize", "landing-zone", "dev-platform", "template"]
  maintainers:
    - user: "lukas.weberruss"
  steps:
    - style: "compass"
      id: "identify-workload-needs"
      title: "Identify the Workload Needs"
      trailContext: "Use discovery findings and the chosen migration strategy to identify the project environment, network relationships, service needs, and owning team."
      pageId: "migration/design-and-mobilize/landing-zones/application-landing-zone#why-it-depends-on-discovery"

    - style: "hut"
      id: "open-workspace"
      title: "Open the Application Workspace"
      trailContext: "Open the Configurator, sign in with STACKIT, and select the working environment for your organization. Establish the Application Owner and the platform team's points of contact."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#start-in-your-workspace"

    - style: "chart"
      id: "understand-template-versions"
      title: "Understand the Published Offering"
      trailContext: "Use a published project template as the reviewed platform offering. Identify its version, fixed settings, allowed parameters, and intended target before placing the order."
      imageSrc: "contributors/stackit/files/migration/landing-zone-configurator-template-lifecycle.svg"
      imageAlt: "An immutable template version feeds separate application instances; later versions become explicit new catalog choices"

    - style: "gondola"
      id: "choose-template"
      title: "Select the Offering and Set Project Parameters"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#order-an-application-landing-zone"
          cards: false
      right:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#provide-project-parameters"
          cards: false

    - style: "shield"
      id: "place-order"
      title: "Place and Approve the Order"
      trailContext: "Place the order for the selected template version and follow its configured approval policy. Keep the order as the reference for the concrete application instance."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#place-and-approve-the-order"

    - style: "chart"
      id: "review-application-plan"
      title: "Review the Plan and Start Deployment"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#review-and-create-the-application-environment"
          cards: false
      right:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#apply-the-application-plan"
          cards: false

    - style: "shield"
      id: "validate-environment"
      title: "Validate the Delivered Environment"
      trailContext: "Validate the resulting project and agreed access. Record the owning team, project and network references, services, and operational contact for the workload delivery team."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#validate-the-application-environment"

    - style: "gondola"
      id: "prepare-workload-handoff"
      title: "Prepare the Workload Handover"
      trailContext: "Review application-specific access, connectivity, observability, and recovery arrangements. Carry the environment references into the workload runbook and agree the migration readiness decision."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#hand-over-to-workload-migration"

    - style: "stairs"
      id: "connect-migration-use-case"
      title: "Connect the Migration Use Case"
      trailContext: "For a VMware Relocate wave, continue with the VM Application Landing Zone blueprint and the selected migration tool runbook. For other workloads, follow the corresponding target design and delivery path."
      assetId: "migration/assetcontainer/stackit/vm-application-landing-zone-relocate.mdx#landing-zone-and-workload-boundary"

    - style: "summit"
      id: "operate-instance"
      title: "Own and Evolve the Instance"
      trailContext: "Keep instance history and operational ownership visible. Review drift and later changes deliberately, feed improvements into future template versions, and plan environment retirement as an explicit activity."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#operate-and-evolve"

  presentations:
    - id: "application-owner-demo"
      label: "Application Owner demo"
      description: "A focused demonstration from the published catalog to an application environment and workload handover."
      preset: "minimal"
      agenda: false
      steps:
        - "open-workspace"
        - "choose-template"
        - "review-application-plan"
        - "prepare-workload-handoff"
    - id: "self-service-walkthrough"
      label: "Self-service walkthrough"
      description: "The complete Application Owner journey from workload requirements through ordering, deployment, and operations."
      default: true
      launch: true
      preset: "focus"
      steps:
        - "identify-workload-needs"
        - "open-workspace"
        - "understand-template-versions"
        - "choose-template"
        - "place-order"
        - "review-application-plan"
        - "validate-environment"
        - "prepare-workload-handoff"
        - "connect-migration-use-case"
        - "operate-instance"
source_url: "https://framework.stackit.cloud/migration/trails/stackit/landing-zone-configurator-self-service/"
source_file: "docs/migration/trails/stackit/landing-zone-configurator-self-service.mdx"
---

## Steps

### 1. Identify the Workload Needs

Stage: `compass`

Use discovery findings and the chosen migration strategy to identify the project environment, network relationships, service needs, and owning team.

Page: [/migration/design-and-mobilize/landing-zones/application-landing-zone/#why-it-depends-on-discovery](/migration/design-and-mobilize/landing-zones/application-landing-zone/#why-it-depends-on-discovery) — source: [/raw/migration/design-and-mobilize/landing-zones/application-landing-zone.md](/raw/migration/design-and-mobilize/landing-zones/application-landing-zone.md), section `#why-it-depends-on-discovery`

### 2. Open the Application Workspace

Stage: `hut`

Open the Configurator, sign in with STACKIT, and select the working environment for your organization. Establish the Application Owner and the platform team's points of contact.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#start-in-your-workspace](/migration/assetcontainer/stackit/landing-zone-configurator/#start-in-your-workspace) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#start-in-your-workspace`

### 3. Understand the Published Offering

Stage: `chart`

Use a published project template as the reviewed platform offering. Identify its version, fixed settings, allowed parameters, and intended target before placing the order.

### 4. Select the Offering and Set Project Parameters

Stage: `gondola`

### 5. Place and Approve the Order

Stage: `shield`

Place the order for the selected template version and follow its configured approval policy. Keep the order as the reference for the concrete application instance.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#place-and-approve-the-order](/migration/assetcontainer/stackit/landing-zone-configurator/#place-and-approve-the-order) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#place-and-approve-the-order`

### 6. Review the Plan and Start Deployment

Stage: `chart`

### 7. Validate the Delivered Environment

Stage: `shield`

Validate the resulting project and agreed access. Record the owning team, project and network references, services, and operational contact for the workload delivery team.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#validate-the-application-environment](/migration/assetcontainer/stackit/landing-zone-configurator/#validate-the-application-environment) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#validate-the-application-environment`

### 8. Prepare the Workload Handover

Stage: `gondola`

Review application-specific access, connectivity, observability, and recovery arrangements. Carry the environment references into the workload runbook and agree the migration readiness decision.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#hand-over-to-workload-migration](/migration/assetcontainer/stackit/landing-zone-configurator/#hand-over-to-workload-migration) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#hand-over-to-workload-migration`

### 9. Connect the Migration Use Case

Stage: `stairs`

For a VMware Relocate wave, continue with the VM Application Landing Zone blueprint and the selected migration tool runbook. For other workloads, follow the corresponding target design and delivery path.

Asset: [/migration/assetcontainer/stackit/vm-application-landing-zone-relocate/#landing-zone-and-workload-boundary](/migration/assetcontainer/stackit/vm-application-landing-zone-relocate/#landing-zone-and-workload-boundary) — source: [/raw/migration/assetcontainer/stackit/vm-application-landing-zone-relocate.md](/raw/migration/assetcontainer/stackit/vm-application-landing-zone-relocate.md), section `#landing-zone-and-workload-boundary`

### 10. Own and Evolve the Instance

Stage: `summit`

Keep instance history and operational ownership visible. Review drift and later changes deliberately, feed improvements into future template versions, and plan environment retirement as an explicit activity.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#operate-and-evolve](/migration/assetcontainer/stackit/landing-zone-configurator/#operate-and-evolve) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#operate-and-evolve`

