I currently have around 15 automated workflows in Zapier that handle basic tasks like connecting Google Sheets with Gmail and similar integrations. Since these automations don’t run frequently throughout the month, the costs are adding up and I’m looking to switch everything over to Make to save money.
Does anyone know if there’s a straightforward method to transfer existing Zapier automations into Make scenarios? I’m hoping there might be an import feature or some other efficient approach rather than rebuilding each workflow from scratch.
just rebuild em manually - no magic transfer button lol. did this 4 months ago with 15 workflows too. for basic Google Sheets + Gmail stuff like yours, it’s sort of straightforward once u get the hang of Make’s module system. but don’t try doing all 15 at once, you’ll lose ur mind.
no magic import button exists - i searched everywhere when i switched last year. but rebuilding isn’t awful if you’re systematic about it. screenshot your zaps first for reference, then rebuild one workflow at a time. make’s interface feels strange at first, but connecting modules becomes natural once you get it.
No direct migration tool exists between Zapier and Make - you’ll have to rebuild everything manually. But it’s not as bad as it sounds since you’ve already figured out the logic in Zapier. I switched about 8 months ago with around 20 workflows. Document each Zapier step first - it makes the whole process way smoother. The biggest hurdle is Make’s different terminology and how it sometimes needs multiple modules for what Zapier does in one step. For basic Google Sheets and Gmail stuff like yours, Make’s modules are pretty straightforward. Start with your simplest workflow to learn the interface, then move to the complex ones. The upfront work is worth it for the cost savings.
Been through this exact migration headache with multiple companies. Both previous answers are right about no direct import, but honestly rebuilding workflows one by one just burns time you don’t have.
Here’s what I learned - the real issue isn’t moving from Zapier to Make. You’re still stuck maintaining workflows manually every time something breaks or needs updates.
Instead of switching between platforms that do the same thing, jump to something that actually scales better. I’ve been using Latenode for similar setups and it handles Google Sheets to Gmail workflows without Make’s multiple modules complexity.
The visual workflow builder makes sense immediately, and you’re not dealing with Make’s learning curve on top of rebuilding everything. Plus the pricing works better for infrequent runs like yours.
No automated migration from Zapier to Make - you’ve got to rebuild everything manually. I did this transition about six months ago with 12 workflows. Took me two weeks of evening work, but the monthly savings made it worth it.
I made a simple spreadsheet tracking each Zapier workflow - triggers, actions, filters, conditions. Really helped me spot patterns and group similar workflows together. Make’s module system threw me off at first since one Zapier step sometimes needs 2-3 Make modules, but their Google Workspace docs are solid.
Big tip - test your rebuilt scenarios with real data before killing the Zapier versions. Caught several mapping errors that would’ve bit me later. There’s a learning curve but it’s not bad for basic integrations like yours.
No migration wizard or import tool exists between the platforms. I made the switch from Zapier to Make about 18 months ago with similar volumes - the rebuild wasn’t too bad once I got into a rhythm. I grouped my Zapier workflows by complexity instead of rebuilding randomly. Tackled the critical ones first in case I hit any walls. Make’s error handling actually beats Zapier’s for Gmail and Google Sheets connections - nice bonus. Make handles data structures differently than Zapier, which caught me off guard. It processes arrays and complex objects in its own way. Your Google Sheets workflows will probably need iterator modules if you’re working with multiple rows. The Make community forum has good examples for common Gmail automation patterns that’ll save you debugging time.