--- title: Repurchase description: Repurchase replaces existing solutions with fit-for-purpose offerings from the STACKIT ecosystem when business value is higher than technical migration effort. sidebar: label: Repurchase order: 4 source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/design/repurchase/" source_file: "docs/migration/design-and-mobilize/design/repurchase.mdx" --- ## Understanding Repurchase Repurchase replaces existing systems with alternative solutions instead of migrating the old stack as-is. In migration programs, this is often the best path when the current solution has high modernization cost and low strategic value. Repurchase is not a pure software procurement decision. In most cases, it requires redesigning and adopting a new target operating process, including roles, controls, integrations, and governance. ## Scope for This Design Baseline For this phase, evaluate repurchase options explicitly for these STACKIT-related solutions: - **Workspace by STACKIT** - **ServiceNow on STACKIT** - **RISE with SAP on STACKIT** - **STACKIT Domain Solutions** Other repurchase targets can be added in later iterations. ## When Repurchase Is a Good Fit - **Legacy replacement is cheaper than migration** across lifecycle and operations cost. - **Process standardization goals** are better served by a new solution model. - **Vendor-supported capabilities** reduce custom engineering and operational burden. - **Compliance and sovereignty requirements** are easier to fulfill in the replacement setup. ## Process Transformation Is Mandatory In this framework, Repurchase means process migration, not only product replacement. - **Process design first**: Define the target process model before finalizing tool configuration. - **Role and ownership changes**: Clarify new responsibilities, decision paths, and support model. - **Integration redesign**: Adjust data flows, interfaces, and control points to the new process model. - **Adoption and enablement**: Train users and service teams on new operational behavior, not only on UI. ## Solution-Oriented Design Focus Assess collaboration and workplace process migration, identity integration, and user adoption planning. Evaluate ITSM/ITOM process fit, workflow migration, data mapping, and integration boundaries. Evaluate SAP landscape transition path, governance model, and business continuity requirements. Evaluate domain-specific fit, regulatory alignment, and operational handover requirements. ## Recommended Design Flow 1. Define repurchase candidate scope and business outcomes. 2. Compare migration-of-old vs replacement-of-solution across risk, cost, and timeline. 3. Design the target business process model before finalizing product setup. 4. Design integration model, control model, and data transition approach. 5. Validate process fit with business owners and operations teams in walkthrough sessions. 6. Define cutover and coexistence model for business continuity. 7. Finalize adoption, training, and support transition plan. ## Required Outputs ### Shared outputs across all migration paths - Approved design decision record with scope, assumptions, and governance sign-off. - Validation evidence package for security, compliance, and operational readiness. - Strategy-specific migration runbook draft from the Design phase. - Handover package for Migration Factory Setup and wave planning. ### Repurchase-specific outputs - Repurchase business case with decision criteria. - Target solution architecture and integration design. - Data transition and coexistence strategy. - Cutover and rollback/contingency plan. - Adoption and operations handover package. ## Diagram Step Reference ### Purchase COTS/SaaS and licensing Define the selected replacement solution, licensing model, and governance boundaries. Include operating responsibilities, sovereignty constraints, and contractual checkpoints so target solution decisions remain executable in delivery waves. - Business Case Overview - Security and Compliance ### Migrate business process Describe the business-process transition and operational adoption path. Define process ownership transfer, coexistence period controls, and user enablement milestones so the organization can adopt the new solution model without service disruption. - Runbook Blueprint - Migration Plan - Operating Model Handover