Celigo gave us a dependable backbone for our order-to-cash process. The Salesforce-to-NetSuite flows for accounts, contacts, and opportunities keep customer data consistent across both systems, and the financial flows that bring invoices and credit memos back into Salesforce give Sales and Finance the same view of what a customer has been billed. Because the flows are configurable, we could tailor field mappings, filters, and transformations to our own business rules instead of changing our process to fit the tool.

Cash Application Manager has been a standout. It automates matching incoming payments to open invoices, which cuts down on manual reconciliation work for Finance. It was also manageable when we needed to change our banking setup. We moved our bank connection to a new institution and could reconfigure the setup without rebuilding our cash application process from scratch.

Visibility is another strength. The dashboard shows which records succeeded or failed and why, and lets us retry or fix errors in place. That makes it easy to spot a contact or invoice that didn’t sync and resolve it before it affects billing or collections.

Support has been excellent. The Celigo team is responsive and knowledgeable, and they work through the specifics of our configuration rather than just pointing to documentation. During our CAM bank change, that hands-on help made the transition smoother. Review collected by and hosted on G2.com.

My main frustrations are around the edges rather than the core product. Debugging complex flows can be time-consuming. When a record fails deep in a multi-step flow with transformations, lookups, and scripts, the error message doesn’t always point to the exact cause, so we spend time tracing it by hand. More detailed error context and better step-level logging would help.

Changes to a production flow can also feel riskier than they should. Testing options for a flow that is already live are limited, so we tend to build a copy of the flow in a sandbox or run it against a single record first. A cleaner way to promote and version changes between environments would make that safer.

Finally, the learning curve is real. The platform is flexible, but getting the most out of it, especially hooks, scripting, and advanced mappings, takes time and some hands-on experience. The documentation covers the basics well, but more worked examples for complex scenarios, like multi-object syncs and error-retry patterns, would speed up onboarding for new admins.

None of these are dealbreakers, and support has helped us through the harder cases, but they are the areas where we’d most like to see improvement. Review collected by and hosted on G2.com.