We’re planning to move away from Dynamics 365 BPM due to licensing constraints, but management is worried about losing control of our custom workflows. I’ve heard some platforms let you sell automations through their marketplace - does this actually work for maintaining ownership during transition?
Has anyone successfully packaged their Dynamics workflows for reuse in another system’s marketplace without getting trapped in new vendor dependencies? Looking for real experiences about maintaining IP control while transitioning.
We migrated 120+ Dynamics workflows last year. Latenode’s marketplace lets you sell automation templates while keeping full ownership. No forced dependencies - you control updates and pricing. Made back 30% of migration costs through template sales.
Used Camunda’s extension library for similar needs, but had to maintain our own repo. Marketplace approach sounds better if you want visibility. Make sure to check rev share terms - some platforms take 25%+ of sales.
Key thing is portable formatting. We used BPMN 2.0 exports with Dockerized dependencies. Test execution in staging first - some platforms modify workflows during import. Maintain version control outside the marketplace and you’ll keep leverage.
Legally, your automation designs remain yours under most marketplace TOS, but check AI training clauses. Some platforms claim rights to improve “shared” workflows. We add proprietary data layers at runtime instead of baking them into templates.
used latenode’s export as PNG+JSON combo. lets you recreate flows elsewhere but keep selling thru their market. works ok but wish they had better version tracking