When a sandbox works the way you want, a promotion copies its setup and the master data people entered into a production company. First you plan it: the plan lists every item that would copy and what would happen to it. Nothing in production changes while you plan.
What a promotion is
A promotion creates or updates a production company from a sandbox. It copies the setup and the master data, never the practice records. The sandbox stays exactly as it was: it is only read.
Owners and administrators of the organization that receives the copy plan promotions, from Promotions in the organization's menu. On the organization's overview, under Sandboxes, you can also select Promote to production.
Plan a promotion
- Open Promotions in the organization and select Plan a promotion.
- Under Sandbox, choose the sandbox to copy from. You see the sandboxes you administer, in any of your organizations.
- Under Production company, choose An existing production company of this organization, or A new production company with its name and URL identifier. A new company is created only when the promotion runs.
- Under What to copy, untick the sections you want to leave out. All are ticked at first.
- Select Plan. The plan opens.
What copies
Company settings, work types and stages, products, partners, sites and plots, members and their roles, integration settings (never their credentials), webhook and inbound endpoints, lot rules, automations, controls, dashboards and report schedules. In an existing company, items match by external reference, then by name, so each one shows Create, Update or Keep as is.
What never copies
Lots, movements, processing, readings and field events; certificates; approvals and requests; demo data and anything simulated or from a test connection; the ledger history; TRACES statements; reports and exports; the audit history; keys, passkeys, API keys and secrets; assistant conversations. The plan lists demo and simulated items as Not copied, so you see they stay behind.
Personal data between organizations
Inside one organization, personal data copies with the items. When the sandbox belongs to another organization, the copy goes to another controller of the data, so people's names, tax IDs, contacts, addresses and members' e-mails stay behind by default. A partner who is a person stays behind with their farms and plots. Tick Include personal data only when the sandbox's organization has a lawful basis to share them, such as a written agreement or the people's consent. A deletion request in one company does not reach the other: each keeps its own copy.
Fix conflicts
An item marked Conflict is not copied. Each one says what happened, why, and how to fix it, for example two items with the same reference but of different kinds, or a setting the organization locked. Fix it in the sandbox or in production, then select Plan again. Planning again uses the same choices and refreshes the plan with the sandbox and production as they are now. Cancel plan closes a plan without changing anything.
Request the promotion
A plan changes nothing until it is requested and approved. Open the plan in Promotions and select Request promotion, add a note for the approver if you like, and confirm with your second factor. The plan is frozen: what the approver sees is exactly what will copy. If the sandbox or production changed since you planned, the request is refused; select Plan again, check the new plan, then request it.
Approve or reject
A second owner or administrator of the production company approves the request: open the plan in Promotions, read it, and select Approve, confirming with your second factor. When the production company has another owner or administrator, whoever requested the promotion can never approve it: four-eyes applies, and one of the others approves.
When you are the only owner or administrator of the production company (and of its organization), nobody else can approve. The plan then offers Approve as the only admin: you approve your own request with your second factor, and it is recorded as self-approved by the sole admin. Anyone who becomes an owner or administrator of the organization later gets a notice about it. To have four-eyes instead, invite a second administrator in Organization → People with the role Admin before you approve; from then on, they approve.
The approval is refused when the sandbox or production changed since the request; the plan then has to be made again. Reject closes a requested promotion without copying anything.
The people involved are told on their bell, with a link to the promotion: the owners and administrators who can approve when a promotion waits for them, and the requester when it is approved, rejected, completed or failed. The plan shows everyone by name: who requested it, who approved it and who gave the other organization's OK.
They also get an e-mail with the same link. When the promotion goes into another organization whose production company does not exist yet, no bell holds the notice: its owners and administrators get it by e-mail, and the organization's activity log records it.
A sandbox of another organization
When the sandbox belongs to another organization, its data goes to another controller, so an owner of that organization also gives their OK. They find the request in their own Promotions page, under From this organization, and select Approve with their second factor, or Reject. The owners of that organization get a notice when a promotion waits for them. Whoever requested the promotion never gives this OK when the organization has another owner. When the requester is that organization's only owner, their request is its OK, recorded the same way as a self-approval by the sole admin. The run starts once both approvals are in.
The run
Once approved, the promotion runs on its own, section by section: the company, work types and stages, products, partners, sites, settings, members, integrations, endpoints, lot rules, then the other drafts. The page shows its progress.
- A new production company is created in the chosen organization. You are its owner, and the organization's owners and administrators become its administrators.
- Products of the organization's catalog stay linked to it: inside one organization, production uses the same catalog entry as the sandbox, never a second copy of it.
- Members receive an invitation with the same role. Nobody gets an account or access until they accept it and set up their authenticator app.
- Integrations become Live connections that need credentials: nothing secret is copied. When you open the integration's connect form, the settings from the sandbox are already filled in, so you only add the credentials. Set aside removes one you do not need. Home lists what is left.
- Lot rules are ticked in the company setup with the options and settings chosen in the sandbox. They are turned on through the production ledger's own start and its approval, never from the sandbox's test ledger.
- Automations, checks, dashboards, report schedules and endpoints arrive as drafts or paused, as with a setup file. When production already has one with the same name, production's version is kept.
- A site whose partner is not in production is not copied, and the report says why.
Read the result
When the run ends, each item shows Created, Updated, Kept as is, Not copied or Failed, and a link to the item in production. An item not copied or failed says what happened, why, and how to fix it. A failed item stops only the rest of its section; everything else is copied. Both companies keep an audit line: the sandbox says where it was promoted to, production where it came from. The sandbox itself never changes.
Retry a failed run
Fix what failed (each failed item says how), then select Retry and confirm with your second factor. The run continues where it stopped: what was already copied is matched and never copied twice.
Promote again
After a run, the sandbox and production can keep changing. Select Promote again on a completed promotion to plan a new one from the same sandbox into the same company. Items match what the last run made, so the plan shows only what changed. It is requested and approved like the first one.
Stop a promotion
Select Cancel to close a promotion at any point before its run ends: planned, requested, approved, running or failed. A run in progress stops after the item it is copying; what it already copied stays in production.