Off AWX in four milestones.
Fixed price, evidence carried forward.

We move you off AWX, Semaphore, or Rundeck and into production on SwitchTender, with the change controls you already run and your evidence workflows carried forward. Milestones are scheduled around your access, approvals, credential owners, and production change windows, and a delay in any of those moves the affected milestone. The four milestones are normally completed over about six weeks once the readiness items below are in place.

Before milestone one begins

• Access provisioned to the environment, the repositories, and the target hosts.
• One named technical counterpart who can coordinate access and answer migration questions within a business day.
• The people who hold your credential values, since exports never contain secrets.
• A representative set of production workflows chosen and recorded for validation, so we agree up front what "working" means.
• Someone who can decide approval policy, and someone who can authorize the production cutover. Often two different people.

The four milestones

1. Discovery and import. We inventory what you have, run the import, and show you item by item what was in the old controller and what landed.
2. Environment. SwitchTender deployed on your infrastructure, sized to your fleet, wired to your identity provider, with credentials entered by their owners and exercised against the recorded validation set.
3. Governance. Approval policy built from the change process you already run, agent policy for anything proposing changes automatically, and evidence configured against the controls you identify with us during discovery.
4. Cutover and handoff. The validation set recorded in milestone one runs green, meaning every workflow in it completes with a zero exit status, which is what finishes this milestone rather than an open-ended parallel period. You authorize the cutover through your own change process, and you get runbooks and a working session, because your team owns this when we leave.

At handoff you have the migrated configuration running in your environment, documented identity and governance configuration, the recorded validation set passing, evidence configured against your controls, production runbooks, and a team that has been walked through all of it.

Flat $25,000 for a standard migration: one source controller, one production environment, standard integrations. Playbook and host counts do not set the price by themselves, because the importer handles bulk. We scope together first when the work changes in nature rather than size, such as multiple independently operated environments, custom execution dependencies or plugins, nonstandard network paths, air-gapped targets, or complex identity and secret-store integration. We will tell you which of those you have during the first conversation, not after you have paid.

Migration reproduces the agreed behavior of your source controller for the recorded validation set. Anything that also fails in the source environment is outside migration scope, as is new automation, architectural redesign, and rewriting existing content. We flag whatever we find early and quote it separately if you want it fixed. Work runs under a mutual NDA and a fixed-price statement of work with the milestones above. Every migration is scheduled against our capacity before it starts, and once the statement of work confirms a start date, that date is held for the engagement. Your first year of Team at the 250-host band is included, and a larger band adds the difference for that year: $8,100 at 500 hosts, $26,100 at 1,000, and $44,100 unlimited. The SSO and policies we wire in milestones two and three keep working after cutover. Upgrade to Enterprise within a year and $10,000 of the program price credits toward it.