Smart Mover EOL: for many workflows, n8n is the more direct successor
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 a migration problem with an expiration date.
Connect is the official strategy, but not the right fit for every setup
WoodWing positions Connect as the official integration strategy. Connect is an iPaaS platform built on Workato with 1000+ pre-built connectors and a clear strength in API-driven SaaS workflows. Cloud-first, recipe-based, enterprise iPaaS.
For the typical Smart Mover installed base, however, the architecture often does not match. Smart Mover ran on-premise, with RB Scripts, XML/XSL transformations, FTP paths, IMAP polls, often deeply integrated with custom publishing workflows. This audience is structurally closer to the n8n market than to the cloud iPaaS market.
For these workflows, n8n is the more direct successor
n8n maps Smart Mover logic structurally differently than Connect, specifically along the properties that define the Smart Mover profile:
- Self-hosting on your own infrastructure, free under the fair-code model. GDPR and data sovereignty without cloud lock-in.
- Code nodes (JavaScript, Python) for existing RB Script logic, XML/XSL transformations, SQL calls.
- 400+ integrations plus a generic HTTP request node for any REST API not available as a connector.
- Custom nodes for the publishing-specific integrations that generic iPaaS platforms lack.
For 3f8h.net specifically: The WoodWing Assets Node maps Login, Search, Create, Update, History, Download, and more directly as n8n nodes. The callas pdfToolbox REST Node handles preflight, correction, conversion, splitting, layer operations, and dieline extraction via the callas pdfToolbox REST API. With these, Smart Mover WoodWing PDF pipelines can be transferred to the n8n model largely 1:1.
What 3f8h.net brings to the table
- 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 and callas pdfToolbox REST API, both actively maintained
- Custom scripts for WoodWing Assets (Forensic, ConfigCharm, MissingMaintenance, AltTextCreator, SpeechToText) as evidence of publishing depth beyond the n8n layer
When Connect or Switch is the better fit
If Smart Mover primarily orchestrated cloud integrations in your environment, ties in SaaS sources, runs well on standard connectors, and a cloud architecture is strategically desired: Then Connect is the clean path. Workato iPaaS with 1000+ connectors is strong for exactly this segment.
If Smart Mover primarily handled file-based PDF pipelines in the MB to GB range (preflight, conversion, imposition, color management): Then Enfocus Switch is the more direct successor than n8n. Hot folder architecture, native callas and PitStop integration, optimized for high data volumes.
We deliver tool-neutral consulting. If Connect or Switch is the better answer for your setup, we say so.
The complete three-way comparison
This story is a deliberate pitch for n8n as the pragmatic Smart Mover successor. For a side-by-side comparison of WoodWing Connect, n8n, and Enfocus Switch, see our three-paths migration story: decision map per workflow profile, comparison table, four-phase migration path, ten FAQs.
Frequently asked questions about n8n as Smart Mover successor
Why is n8n the more direct Smart Mover successor than WoodWing Connect?
Smart Mover ran on-premise with RB Scripts, XML/XSL transformations, FTP paths and IMAP polls. n8n maps this profile via self-hosting, code nodes and a generic HTTP request node. WoodWing Connect, as a cloud iPaaS built on Workato, is architecturally further away from the typical Smart Mover setup, even though it is positioned as the official vendor strategy.
Which Smart Mover functions can be mapped 1:1 in n8n?
File operations, FTP, IMAP, webhook reception, SQL calls, XML/XSL transformations and RB Script logic. Our custom nodes add the publishing-specific integrations: WoodWing Assets (Login, Search, Create, Update, History, Download) and callas pdfToolbox REST (preflight, correction, conversion, splitting, layer operations, dieline extraction).
How does n8n support GDPR requirements that Smart Mover already met?
n8n runs self-hosted on your own infrastructure (Docker, Kubernetes, on-premise). Data sovereignty stays fully in house, without third-party cloud as with pure iPaaS platforms. For publishers, banks and insurers who deployed Smart Mover precisely for the on-premise architecture, this is the decisive difference from Connect.
What does n8n cost compared to Smart Mover plus Connect?
n8n self-hosted is free under the fair-code model. The only ongoing costs are your own infrastructure and, optionally, n8n Cloud if self-hosting is not desired. WoodWing Connect is subscription-based with Workato iPaaS pricing. For comparable workflow volumes, n8n is typically significantly cheaper on license, with implementation and maintenance effort as the main cost factor.