N8N ONE-WORKFLOW MIGRATION EVIDENCE CHECKLIST
Agent Rescue Desk
https://agent-rescue-desk.netlify.app/n8n-workflow-migration-rescue

PURPOSE

Use this worksheet to preserve the observable contract for one already-running
workflow before its source platform becomes unavailable. Complete it locally.
Redact it before sharing. This is an evidence inventory, not a credential
collection form.

NEVER INCLUDE

- passwords, API keys, bearer tokens, private keys, cookies, or recovery codes
- credential values, connection strings, webhook secrets, or private URLs
- live customer records, regulated data, or unrelated production data
- identity documents, payment-card details, or banking information

1. SOURCE ACCESS AND EXPORT DEADLINE

Source workflow platform:
Source platform family (Zapier, Make, proprietary AI workflow, other):
Access ends or is expected to become unreliable on:
Person or organization authorized to export the workflow:
Available export formats:
Available execution or run-history formats:
Platform-specific nodes, prompts, models, scripts, or assets not included in export:
Last date a complete source behavior check was performed:
Hash or version identifier for the retained source export:

SOURCE-SPECIFIC SEMANTICS TO PRESERVE

For a Zapier Zap, record:
- trigger and action steps
- Filters, Paths, delays, loops, code, and webhook behavior
- relevant task-history evidence and app-specific behavior

For a Make scenario, record:
- modules, routers, filters, iterators, and aggregators
- bundle shapes, scheduling, webhook processing order, and error behavior
- relevant scenario-history evidence

For an AI workflow platform, record:
- prompts, model roles, tool-call and structured-output contracts
- memory, guardrail, retry, branch, and human-handoff behavior

For any source, record behavior and evidence rather than credential values.

2. ONE REPRESENTATIVE WORKFLOW

Workflow name or redacted identifier:
Business purpose:
Trigger type (schedule, webhook, event, manual, other):
Trigger contract, excluding secret values:
Expected invocation frequency:
Source nodes or steps in order:
Meaningful branches and their conditions:
Retry, timeout, deduplication, and error behavior:
Manual approvals or human handoffs:
External APIs and services, by public product name only:
Data stores and record types, excluding live values:
Prompts and model roles, using redacted or synthetic content:
Final downstream side effects:
Observable business outcome that proves success:

3. CREDENTIAL BOUNDARY

List credential TYPES, OWNERS, and ROTATION RESPONSIBILITY only. Never record
credential values here.

Credential type:
Owning system or team:
Required permission boundary:
Target n8n credential owner:
Rotation or revocation dependency:

Repeat as needed.

4. REPRESENTATIVE SANITIZED FIXTURE

Fixture identifier:
How the fixture was sanitized:
Synthetic or redacted input shape:
Expected branch:
Expected intermediate state:
Expected final output shape:
Expected downstream side effect:
Single observable pass condition:
Known acceptable nondeterminism:
Known forbidden outcomes:

5. CLIENT VARIATION MATRIX

For each client or tenant class, identify whether these vary. Do not include
actual credential values or customer data.

Credential ownership:
Input schema:
Prompt or model configuration:
Routing and branch rules:
Locale or formatting:
API endpoints:
Data-store schema:
Business rules:
Approval or handoff logic:
Volume and timing:
Retention or compliance constraints:

Classify each variation as:
- configuration only
- requires a workflow branch
- requires a separate workflow
- unknown and must be tested

6. TARGET N8N ENVIRONMENT

n8n Cloud or self-hosted:
n8n version:
Non-production copy available:
Execution-data retention setting:
Queue or worker topology, if applicable:
Public webhook or reverse-proxy boundary:
Required community nodes:
Required code-node runtime or dependencies:
Logging and error-workflow availability:
Person or organization authorized to change the target:

7. CUTOVER AND ROLLBACK

Source workflow freeze point:
Target workflow activation boundary:
Duplicate-side-effect prevention:
Parallel-run or shadow-test plan:
Cutover owner:
Rollback trigger:
Rollback steps:
How the source remains recoverable during verification:
How credentials are revoked after handoff:

8. ACCEPTANCE CONTRACT

One representative trigger:
One sanitized fixture:
One expected branch:
One expected final output:
One observable downstream result:
Maximum acceptable latency:
Required evidence artifact:
Authorized acceptance decision-maker:

9. FIRST-PHASE SCOPE DECISION

In scope:
- one already-running representative workflow
- one representative client or tenant configuration
- one agreed sanitized fixture and expected outcome
- source behavior inventory and portable-contract map
- n8n rebuild or repair in an export, copy, or non-production target
- secret-free export or diff, verification evidence, rollback notes, known
  tenant risks, and a separate rollout estimate

Out of scope unless separately written and accepted:
- additional workflows or full client-fleet replication
- bulk credential migration
- unattended production rollout
- greenfield redesign
- ongoing hosting, maintenance, or staff augmentation
- bypassing access controls, platform policy, or authorization

NEXT STEP

Keep the completed worksheet private. Submit only a short, secret-free summary
for a free fit review:
https://agent-rescue-desk.netlify.app/?source=n8n-workflow-migration#intake

The $1,000 guarded 12-hour service window begins only after cleared payment,
accepted written scope, reproducible source behavior, a testable agreed target
outcome, and the agreed sanitized materials and required access are ready. It
pauses for customer-controlled blockers.