Search guides...
Ctrl K
Teams moving from Octopus Deploy find most of the vocabulary familiar: projects, environments, lifecycles, releases, channels, tags and scoped variables. The migration work is moving those definitions across, re-pointing CI and retiring the old integrations.
How Octopus concepts map
Project
A project is one deployable unit with its own deployment process and variables.
Environment
Development, Staging, Production and so on. Variables and steps are scoped to environments.
Lifecycle and channel
Lifecycles are ordered phases a release passes through. Channels let one project use different lifecycles and version rules.
Release
A snapshot of packages, variables and the deployment process that is promoted unchanged.
Tentacle and agent
Machines run the Jaws Deploy agent, which always connects outbound to Jaws Deploy.
Target roles and tags
Octopus target roles map to Jaws Deploy tags, which scope steps and variables.
What works differently
- Spaces map to workspaces.
- Library variable sets map to workspace variables, which projects import.
- Step templates and script modules exist in Jaws Deploy too, and belong to a workspace.
- Runbooks and manual intervention steps have no equivalent in Jaws Deploy. Keep those tasks in a script step or outside the deployment process.
A migration path
- Pick one Octopus project and recreate it by hand in Jaws Deploy. For a single project this is usually quicker than building an import.
- Run both side by side for one release cycle.
- Point CI at the new project and retire the Octopus project.
- Move the next project the same way.
Don't try to move everything at once. Running both in parallel shows the differences in a deployment process that an export file doesn't.
The Fleet and Dedicated plans include help with migrating from Octopus Deploy. See pricing for the plans.