Your team relies on an automation that gathers leads, updates the CRM, and sends a daily report. The person who built it is leaving. Nobody is sure which account runs it or where the connections are managed.
The workflow diagram is only one part of the handover. The business needs ownership of the accounts, permissions, credentials, and operating knowledge that keep the work running.
Map the dependencies before changing access
Imagine a hypothetical workflow connecting a form, spreadsheet, CRM, and email service. The automation platform may belong to the company while its spreadsheet connection uses an employee's personal authorization. Removing that employee's access can break a different part of the chain.
Create an inventory with one row per dependency. Record the service, business owner, authorized administrators, connection type, purpose, and renewal or billing responsibility. Record where credentials are managed; do not paste secret values into the inventory.
Also identify where outputs go, who receives failure alerts, and what work accumulates when the automation stops. These details determine whether an interruption causes inconvenience, missed customers, or duplicate actions during recovery.
Transfer ownership using the service's supported controls
Use company-controlled accounts and the provider's supported organization, role, transfer, or service-identity features. The appropriate mechanism depends on the service and its plan. A shared password for the departing employee's account is a poor substitute for named access and an accountable owner.
Give each connection only the access it needs. Establish a second authorized operator where appropriate, along with controlled access to recovery methods. Changing a billing contact alone does not transfer technical ownership.
Some connections will need to be authorized again under the new identity. Others may require replacing keys or changing the workflow configuration. Confirm the supported process before assuming an exported workflow includes everything needed to run it.
Test the replacement before the final cutover
Use test records and controlled destinations to verify the replacement connections. Check that the new operator can run the workflow, inspect failures, and stop it when necessary.
Plan the cutover so two active copies cannot process the same real event unintentionally. Decide how to handle work in progress and how to reconcile anything interrupted. Once the replacement is verified, remove old access and rotate affected credentials as appropriate.
A suspected compromise needs a faster containment decision. A routine handover can be prepared in advance so access removal and continuity are handled together.
Make the handover prove itself
Ask the new operator to complete a short rehearsal without the original builder directing every click:
- Identify the last successful run and confirm its business result.
- Investigate a deliberately failed test execution.
- Explain which actions are safe to retry and which could create duplicates.
- Find the escalation contact and pause processing safely.
For n8n workflows, an error workflow can help route execution failures to the responsible person. You still need to define what counts as a failed business result, including cases where a workflow technically finishes.
Five prompts to use with your AI coding assistant
Before you begin: Use the same project conversation for all five prompts. Inspect first, approve the plan yourself, and never test against live customer data or secrets.
These prompts assume your assistant can inspect the relevant project. Ask it to say clearly if it cannot. Use the prompts one at a time, reviewing each response before moving to the next step.
1. Map
Map each critical automation, including its trigger, integrations, credential owner, schedules, outputs, and failure notifications. Indicate missing ownership information without exposing secrets.
2. Audit
Identify dependencies on individual accounts, expired tokens, undocumented permissions, and single-person knowledge. Separate confirmed risks from vendor settings that need an administrator to check.
3. Plan
Propose an ownership and documentation plan using organization accounts or service identities where supported, least-privilege access, runbooks, and named operators.
4. Challenge
Rehearse employee departure, expired credentials, and a failed integration without touching production. Identify transfer limits, administrator approvals, and continuity gaps.
5. Implement
After explicit approval, carry out only authorized test changes, update documentation, and validate handover. Do not revoke live accounts, rotate real secrets, or interrupt production integrations automatically.
DitchNow offers hands-on team enablement and handover. Based in Haarlem, we help founders and teams in Amsterdam and across the Netherlands make their automations maintainable. Book a conversation around one workflow your team needs to own confidently.
About DitchNow
DitchNow is based in Haarlem, Netherlands, and helps founders and teams fix and extend software and put AI to work. Meet DitchNow.