Source-to-target map
Trigger, inputs, transformations, state, irreversible actions, outputs, and substitutions documented before a rebuild.
FREE MIGRATION REFERENCE · ONE WORKFLOW
Map the workflow
before you rebuild it.
When an automation tool closes or a legacy flow becomes unmaintainable, a node-for-node copy is not enough. Builderlog reviews one representative workflow, maps the source and target, identifies three priority migration risks, and defines one acceptance test. Implementation is not included.
This is a written planning review, not a migration build. No passwords, production login, or live customer records are collected.
- 1 workflow family
- 3 priority risks
- 1 acceptance test
- 0 credentials collected
THE MIGRATION TRAP
Equivalent nodes can still produce a different business result.
Trigger semantics: does the replacement start on the same event and replay boundary?
Field lineage: does each value still come from the intended source record?
Side effects: can a timeout after a committed write create a duplicate on retry?
Terminal evidence: can an empty branch silently skip the required outcome?
WHAT COMES BACK
A migration decision you can inspect.
Three priority risks
The highest-risk mapping, retry, state, or missing-evidence problems in plain language and the safest order to address them.
One acceptance test
A reproducible sample input, expected result, observable evidence, and fail-closed behavior.
Provider-ready next step
A clear decision to keep it manual, use a self-serve kit, improve the current workflow, or seek a separately scoped implementation.
GOOD REVIEW
Map one representative path first.
Best for one workflow whose source behavior, sample input, and required outcome can be described without production access.
NOT INCLUDED
What this reference does not include
Workflow construction, client copies, live data migration, account administration, and ongoing support require a separate implementation scope.
3–4 WORKFLOWS × MANY CLIENTS
Do not rebuild every copy first.
If one workflow is repeated across many client environments, the first deliverable should be a tenant-neutral contract—not dozens of edited copies. Separate shared workflow logic from validated client configuration, prove one synthetic tenant boundary, and deploy to one canary before any fleet rollout.
The free reference maps one representative workflow family, a tenant-neutral configuration boundary, one synthetic canary idea, and rollout/rollback questions. It does not include workflow files, bulk production deployment, live client records, credentials, or fleet management.
- 01 · Shared templateVersion reusable logic once instead of editing every client copy.
- 02 · Client configurationValidate required fields and reject unknown or incomplete tenant settings.
- 03 · Tenant boundaryProve one client's configuration cannot read or update another client's records.
- 04 · Canary + rollbackExpand only after one synthetic tenant passes and the previous version can be restored.
EVIDENCE BEFORE PAYMENT
Inspect the delivery shape—not a fabricated case study.
The public Builderlog reference packet contains three workflow JSON files, anonymous fixtures, an acceptance receipt, a recovery runbook, and a portable verifier. All three JSON files were accepted by the n8n 2.31.0 CLI importer on Node 22; the packet verifier passes 41 structural checks and 11 workflow or topology cases.
This proves importer acceptance and packet integrity only. It is Builderlog-owned reference work—not buyer-specific production execution or a customer result.
Inspect workflows, receipts, and runbook →FAQ
Before purchasing
What fits the review?
One existing workflow or manual process with one primary outcome. The source can be another automation platform, a documented manual process, or a legacy n8n workflow.
Do you migrate live customer data?
No. Builderlog reviews a sanitized export, field map, screenshots, or synthetic examples. Credentials and production records stay in your environment.
What comes back?
A source-to-target map, three priority migration risks, one acceptance test, and a clear next step you can use yourself or give to an implementation provider.
Can this cover several workflows or many client copies?
The review can map one connected workflow family serving one outcome. It does not include builds, production deployment, or account-by-account migration.
Is the former paid review still available?
No. The paid review is no longer available; the free reference sample remains available for reading.
FREE MIGRATION REFERENCE