LaraDep Documentation
You are reading Common
Migration between managed and self-hosted
How to plan and execute mode migration safely: what to verify, what to extract between operating modes, and what to do after migration.
Mode migration
Moving between managed and self-hosted is more than toggling a setting; it is a controlled process migration. This page defines a standard that prevents chaos and supports repeatability.
Who should use this
It is suitable for teams that already run LaraDep in one mode and now need a mode change due to governance, cost, security, or required control level.
Before you start
- Your current onboarding and operational process is documented,
- your team understands both modes at documentation level (managed/self-hosted, first-run, runbook),
- you have a clear decision maker for go/no-go.
Migration process (high level)
- Validate reason: why switching mode matters (costs, controls, compliance, team capacity).
- Map current state: workspaces, templates, roles, deployment history, critical applications.
- Prepare target process: configure onboarding, preflight checks, and runbook for the target mode.
- Pilot migration: choose one pilot environment, verify rollback options, and run first deployment.
- Finalize transition: transfer critical variables, confirm access policy, and publish updated operating standard.
Migration checklist
- Is the mode change approved by a written decision?
- Are new credential workflows and access patterns prepared?
- Is onboarding configured and communicated?
- Have risks and rollback steps been defined?
- Has runbook and change evidence been updated after migration?
Common mistakes
- Skipping a target-mode onboarding step.
- Running migration on production without pilot first.
- Missing role owners for launch and incident ownership.
- Not updating runbook and workspace role rules after the migration.
Next steps
- For decision validation, review managed vs. self-hosted.
- For a production-standard first run, perform first deployment and guided deployment/preflight.
- After mode switch, update roles and access in workspaces and security.
- For operational governance, use runbook and governance and in self-hosted troubleshoot with troubleshooting.
Cross-track links
To return to the original mode, repeat a controlled transition with documented onboarding and preflight checks in managed or self-hosted.
Next step: Review the concrete flow in managed getting started or self-hosted installation.