WoodWing Smart Mover end-of-life: three paths forward
WoodWing has announced the end-of-life for Smart Mover in an official helpcenter notice. Vendor support ended on 27 March 2026; end-of-life follows on 27 March 2027. Anyone running Smart Mover in production today has to act. The question is not whether, but with what and how.
Three realistic paths lead away from Smart Mover: WoodWing Connect, n8n and Enfocus Switch. Each has its strengths, each has its optimal scope.
What Smart Mover was, and why the announcement matters
Smart Mover was WoodWing’s workflow engine for Studio and Assets. The service component ran in the background on Windows, Mac or Linux; the graphical manager for configuration on Windows or Mac. In day-to-day publishing, Smart Mover was often the central glue around the WoodWing stack: moving files, setting metadata, FTP transfers, email imports, RB script execution, XML/XSL transformation, SQL execution.
End-of-support does not erase these functions overnight. But the risk profile shifts:
- From 27 March 2026 onwards, no security updates, no patches, no vendor support
- From 27 March 2027 onwards, incompatibility with newer versions of WoodWing Studio and Assets
- Production outages without an escalation path to the vendor
A planned transition with parallel operation is significantly cheaper than an emergency switch after a production outage.
Three paths away from Smart Mover
Between „do nothing” and „migrate everything” lie three realistic migration paths. WoodWing Connect is an iPaaS platform built on Workato, positioned by WoodWing as the official integration strategy. n8n is a vendor-neutral, fair-code workflow platform with self-hosting option. Enfocus Switch is the established file-centric workflow engine for prepress and publishing production.
| WoodWing Connect | n8n | Enfocus Switch | |
|---|---|---|---|
| Processing model | iPaaS on Workato, recipes with triggers and actions | API calls, webhooks, event-based | hot folders, job tickets, file-based |
| Strength | 1000+ Workato connectors, officially supported by WoodWing | lightweight orchestration, metadata, API bridges | heavy media files, PDF processing in MB to GB range |
| PDF processing | via generic API calls to callas pdfToolbox REST | via callas pdfToolbox REST Node | native via PitStop, callas |
| License | commercial, subscription | fair-code, free for self-hosting | commercial, modular |
| Customization | recipes for 1000+ connectors, custom actions for indirect API calls | full code control, custom nodes | apps, Switch Scripting (JavaScript ES3, Node.js) |
| Data sovereignty | cloud service (Workato US-based) | self-hosting possible | on-premise or cloud |
| Typical fit | enterprise iPaaS integrations with many SaaS sources | API-driven orchestration between systems | classic print production with high data volumes |
This is not a ranking, it is a tool map. Which path is right for you depends on what Smart Mover actually did in your environment.
Which tool replaces Smart Mover for which profile?
Four typical Smart Mover profiles, four recommendations:
- Smart Mover as file mover plus WoodWing sync: n8n with our custom node for WoodWing Assets. Migration is 1:1.
- Smart Mover for high-volume PDF pipelines (preflight, conversion, imposition, color management): Enfocus Switch. File-based, optimized for GB data, native callas and PitStop integration.
- Smart Mover for API-centric workflows with many SaaS integrations: WoodWing Connect, an iPaaS platform built on Workato with 1000+ pre-built connectors. Strong on cloud integrations, officially supported by WoodWing.
- Mixed workflows: hybrid architecture. n8n for the orchestration layer (metadata, status, API bridges), Switch for the heavy lifting (PDFs, print data).
One clarification: anyone running Smart Mover today with RB Scripts and XML/XSL transformations can map this logic into n8n via code nodes (JavaScript, Python). But when the main task is moving large files, n8n is technically not the optimal answer. Switch is often faster and more stable here.
PDF workflows: this is where it gets technical
Smart Mover handled InDesign Server jobs, PDF operations, often a connection to callas pdfToolbox Server. This is the point where migration recommendations diverge.
In n8n via the callas pdfToolbox REST Node from 3f8h.net:
- Preflight, correction (fixups), conversion, splitting, layer operations, dieline extraction
- 9 operations directly available as nodes
- Cloud-compatible, async polling, error-handled
- File input via URL, no multipart uploads
In Enfocus Switch via native PitStop and callas modules:
- Preflight, correction, conversion as integral pipeline components
- Hot folder-based, optimized for GB files
- Color management and imposition deeply integrated
Not every PDF pipeline belongs in n8n. Not every belongs in Switch. For high-volume workflows with GB files, Switch often wins. For API-driven pipelines with URL-based file input, n8n wins.
How does a Smart Mover migration work?
An orderly migration has four phases:
- Inventory: capture all active Smart Mover processes and rate them by criticality. What runs daily, what weekly? Where are single points of failure? Where is consolidation potential?
- Tool mapping: pick the right tool per process (n8n, Switch, Connect or hybrid). Design the target architecture. Define a realistic migration roadmap.
- Step-by-step migration: convert workflows one by one, parallel operation alongside Smart Mover. Test with real production data. No big-bang migration.
- Handover: training for technical staff and business users. Documentation. Optional: maintenance agreement.
Parallel operation alongside Smart Mover ensures there are no production outages during the migration. Effort and timeline depend on the count and complexity of individual workflows and are estimated reliably after the inventory (phase 1).
What 3f8h.net brings to the table
We bring three vendor stacks together as equals: callas, Enfocus and n8n. That is what makes the difference in Smart Mover migrations.
- 25 years of workflow experience in publishing since 1999, DACH focus with dozens of customers worldwide across publishers, print shops, brand manufacturing and banks/insurers with corporate design standards
- Active n8n practice since 2024 in workflow design and implementation projects for clients
- 15+ years of Enfocus workflow experience, Enfocus Gold Partner with certifications as App Developer, Consultant, Reseller and Trainer
- callas Gold Partner and Integration Specialist for nearly two decades, with depth in PDF workflows, color management and prepress
- Custom n8n nodes for the key stacks: WoodWing Assets Node and callas pdfToolbox REST Node, both actively maintained
- Custom scripts for WoodWing Assets: Forensic, ConfigCharm, MissingMaintenance, AltTextCreator, SpeechToText and more
- Tool-neutral consulting: we recommend the right tool, not our own tool
With us, the analysis ends with a tool map that fits your actual workflow mix: the right tool per workflow, hybrid where it makes sense.
Frequently asked questions about the Smart Mover end-of-life
When does support for WoodWing Smart Mover end?
Vendor support ended on 27 March 2026. End-of-life follows on 27 March 2027. From end-of-support there are no more security updates or patches; from end-of-life Smart Mover is no longer compatible with newer versions of WoodWing Studio and Assets.
What are the alternatives to WoodWing Smart Mover?
Three realistic paths: WoodWing Connect (Workato-based iPaaS, the official vendor strategy), n8n (vendor-neutral, fair-code, open source with self-hosting option) and Enfocus Switch (file-centric, with native PDF processing). Which path is right depends on the concrete workflow mix.
Can n8n fully replace WoodWing Smart Mover?
Yes, in terms of functional coverage. All productive Smart Mover functions can be mapped into n8n: file operations, FTP, IMAP, webhook reception, code execution, SQL, image recognition, Slack posts. Custom nodes such as the callas pdfToolbox REST Node and the WoodWing Assets Node from 3f8h.net close the publishing-specific gaps.
Why n8n instead of WoodWing Connect?
WoodWing Connect is an iPaaS platform built on Workato: 1000+ pre-built connectors, cloud-only, officially supported by WoodWing. n8n is vendor-neutral, fair-code with self-hosting option (relevant for GDPR and data sovereignty), 400+ integrations plus a generic HTTP request node and code nodes for JavaScript and Python. The choice is not „simple vs flexible”, but Workato stack on cloud subscription vs n8n on self-hosting.
When is Enfocus Switch the better choice?
Switch is superior for file-centric workflows with high data volumes (PDFs in MB to GB range), native PDF processing (PitStop, callas), color management and imposition. If Smart Mover primarily handled hot folder-based print data workflows in your environment, Switch is the more direct successor than n8n.
What happens to PDF processing after the Smart Mover migration?
Two production-ready paths: in n8n via the callas pdfToolbox REST Node (9 operations for preflight, conversion, splitting, layer operations, dieline extraction, cloud-compatible, async). Or in Enfocus Switch via native PitStop and callas integration (hot folder-based, optimized for GB files). The choice follows the workflow characteristic.
How long does a Smart Mover migration take?
Effort and timeline depend on the count, complexity and integration depth of the individual workflows. We provide reliable estimates after the inventory (phase 1). Parallel operation alongside Smart Mover ensures there are no production outages during the migration, regardless of duration.
How does n8n compare to Smart Mover in cost?
n8n self-hosted is free under the fair-code model, run on your own infrastructure. n8n Cloud is subscription-based, scaled by workflow volume. The main cost factor in practice is not the license, but migration and maintenance effort.
Do I need a WoodWing partner for the migration?
Recommended. Smart Mover migration is not just n8n configuration, but WoodWing understanding (Assets API, Studio workflows, InDesign Server jobs), PDF workflow experience and ideally custom nodes for the most common vendor integrations. Generic n8n providers without a publishing background often fail at exactly these points.
What is 3f8h.net’s migration approach?
Tool-neutral consulting. We analyze existing Smart Mover workflows and recommend the right tool per process: n8n with our custom nodes, Enfocus Switch or WoodWing Connect. Hybrid architectures are possible and often the best answer. Four-phase migration with parallel operation, no big bang.
If n8n is your most likely path: The deep-dive story „n8n as Smart Mover successor” delivers the argumentation specifically for the n8n variant, with Smart Mover-to-n8n mapping in detail.