70+ pre-built connectors and a custom framework for the rest. Mappings in SQL, runs on a schedule or in near real time, lineage you can show an auditor, and a copy of your data in the warehouse of your choice. Integrations stands on its own, between the systems you already run, with no other part of Aquifer required. Add an app later and it runs on the same connections.
Commitments, change orders and invoices move between Procore and the ERP on a schedule or as they change. One mapping, written once, under version control. When a system is not in the catalog, the connector is built on the same framework.
Lineage from source row to destination row, audit logs on every run, and alerts when a schema drifts or a row count moves.
Replicate into Snowflake, Azure Synapse, PostgreSQL or SQL Server, and point Power BI, Tableau, dbt or Excel at it.
Nothing here needs an Aquifer app. If you add one later, it runs on the connections you already built. An Accounting module posts to the ERP you run today, Coordination mirrors the RFIs and submittals Procore owns, and Canvas reads from all of it.
Integrations connects the systems you run, both directions, with the source kept on every value and a copy in the warehouse you choose. When you add an Aquifer app later, it reads the model built from the same connections, and nothing you set up is redone.
Integrations connects your ERPs, project tools, GIS and warehouses to each other and to the Aquifer apps. Pre-built connectors handle auth, paging and rate limits. You focus on the data flowing through.
The same connectors replicate into Snowflake, Azure Synapse, PostgreSQL or SQL Server. Incremental updates sync only what changed. Power BI, Tableau, dbt and Excel read from a warehouse you own.
The same part of the platform, used by the owner, the general contractor and the subcontractor. One example each.
Finance, HR, project and asset systems share one set of project records, so program reports read from the same numbers.
Procore, Vista, Sage 300 CRE, CMiC, Intacct, P6 and Autodesk stay in sync. Commitments, costs and change orders agree without anyone re-keying them.
QuickBooks, Sage 100, Foundation and Assignar connect through templates with guided setup. Timesheets and job costs land in the books without a spreadsheet in between.
Pre-built connectors for the ERPs, project tools, GIS and warehouses construction companies run. When a system is not in the catalog, build the connector on the same framework.
Field mappings, transforms and business rules in plain SQL. Reviewed in a pull request, tested, and versioned like any other code.
Run on a schedule, on a webhook or in near real time. Replay a failed run and backfill a date range from the same console.
Common pairs such as Assignar and Acumatica come as templates with guided setup, so the first sync runs from the template.
Each integration has one schedule and one health status. Press Run now and follow the sync step by step in its history.
Email alerts when a sync fails, and alerts when a source schema drifts or a row count moves away from its baseline.
Every record traced from source to destination, with complete audit logs on every run.
Replicate into Snowflake, Azure Synapse, PostgreSQL or SQL Server. Power BI, Tableau, dbt and Excel read from a warehouse you own.
Run in our cloud, in your VPC or on-prem behind your firewall. Same connectors, same SQL, and your data stays where your policies say.
Integrations needs no other part of Aquifer. If you add an app, what Integrations reads is related into one model of the project that Accounting, Scheduling, Coordination, Canvas and Studio read.
Authenticate to the systems you run with pre-built connectors, or build one on the same framework. Auth, paging and rate limits are handled for you.
Start from a template for a common pair or write the mapping in SQL. Review it like any other code.
Schedule it, trigger it from a webhook or stream it in near real time. One health status, Run now, step-by-step history and an email when a sync fails.
Pricing follows what you use. Every part of the platform can be taken on its own and kept in sync with the systems you already run. Talk to us about pricing for your company.
Talk to us →Do I need the Aquifer apps to use Integrations?
No. Integrations is a product on its own. Connect the systems you run to each other, map the fields in SQL and land a copy in your warehouse, with nothing else from Aquifer. If you add an app later, it runs on the same connections: an Accounting module stays in sync with your ERP through it, Coordination mirrors Procore through it, and Canvas and Studio read what it brings in.
Do I need IT resources to set this up?
IT helps with the first authentication and the security review. Day to day, anyone comfortable with SQL can configure and maintain an integration, and AI coding tools make writing SQL easier than it was.
What happens when a connected system updates its API?
We maintain every connector. When a vendor changes an API, we update the connector, not you.
Can I connect a system you do not have a connector for?
Yes. Custom connectors run on the same framework as the 70+ pre-built ones, with the same schedule, health status and sync history. We also add connectors when customers ask for them.
Do I need to know SQL?
Templates handle the common pairs out of the box. Basic SQL helps when you want to change a mapping or add a business rule.
Which warehouses do you support?
Snowflake, Azure Synapse, PostgreSQL and Microsoft SQL Server. Data lands in a warehouse you own, and Power BI, Tableau, dbt or Excel read from it.
Do you transform the data or just replicate it?
Replication lands the data as it is. Schema design and transforms are yours, in dbt, your BI tool or SQL. The same connectors also drive mapped, system-to-system integrations.
We use a small number of first-party cookies to understand which pages visitors find useful. No advertising, no third parties. Privacy notice
