Migrating to Copilot Studio from Moveworks

Many customers run both M365 Copilot and Moveworks together. Copilot is good at Microsoft stuff, Moveworks is good at handling the rest -- connecting to and actually executing across your third-party systems. And M365 Copilot will be able to call Moveworks directly soon, so they'll work together even better.

Curious to hear from others in the community on this, though!

Hey ​@JenHanley, could you clarify exactly what would be a good example to keep both? - We’re looking to leave Moveworks behind, since I can also develop same customized flows in M365 Copilot like in Moveworks, therefore I’d appreciate your insights.

​@eberteo thanks for your questions.

While you can develop some of the same workflows in MSFT, the question you might ask yourself / your team is if you have the resources to develop and maintain those workflows. 

Though MSFT copilot has a solid extensibility platform and OOTB productivity, it is not designed for Enterprise system operation and the custom workflows do require a level of technical proficiency that is not always scalable for every organization.

Because MW is an Enterprise system automation platform, much of the architectural maintenance is handled by us. What I mean by that is, we work to upgrade models, security, reasoning functionality etc, as part of the platform. We also have built in functionality through our ticketing, search, and provisioning capabilities that do not require you to build or maintain anything. 
 

Therefore, I’d say you should consider the extent to which you are assuming MW and MSFT are comparable / mutually exclusive. 

As a CSM at MW, I’d be happy to meet with you to discuss your business goals and the use cases you are looking to build in MSFT. 

 

Hey ​@mrukavina we can hop on a call, do you have a schedule link to book ?  - Feel free to DM in here. 

​@mrukavina, I have direct messaged you