ERP, CRM and enterprise systems, landed in one place
Data integration services that get ERP and CRM data into Databricks
Our data integration services land data from your ERP, CRM and other enterprise systems in Databricks, governed by Unity Catalog. We use a managed Lakeflow Connect connector where one exists, for Salesforce, HubSpot, Workday or Dynamics 365 apps, and build incremental pipelines where none does, which includes Business Central.
- Who it is for
- Data, finance and operations leaders whose numbers live in five systems
- Bench
- 115+ engineers, 80 Databricks-certified
Most of the work sits in the systems with no connector. Business Central is the one we meet most: Lakeflow Connect's Dynamics 365 connector reads what Azure Synapse Link exports from Dataverse, and Business Central doesn't keep its data in Dataverse. So somebody has to build that pipeline, and own it once it's running.
What we work out first
- Every system holding a number leadership asks about, and who owns each one
- Which sources have a managed connector, which need a pipeline built, and which only ever export files
- How each source reports change: a change feed, a modified timestamp, or nothing at all, which means full reads
- The request limits on the source side, so reporting loads don't spend the quota your users need during the day
- Which keys join the systems, the customer in the CRM against the same customer in the ERP, and what happens when they disagree
- Who may see what once it lands, written as Unity Catalog grants before the first table exists
What we build
- Managed ingestion through Lakeflow Connect where it covers the source: Salesforce, HubSpot, Workday, Jira and SharePoint, and change data capture from SQL Server, MySQL, PostgreSQL and Oracle
- Dynamics 365 apps through the Lakeflow Connect Dynamics 365 connector, which reads the Azure Synapse Link export in Data Lake Storage
- Business Central pipelines built by hand: incremental reads of the API pages filtered on lastModifiedDateTime, or the tables the bc2adls extension exports
- Bronze, silver and gold layers with the joins across systems done once, in one place, instead of again in every report
- Grants, row filters and column masks on the integrated tables, so ledger data stays with the people allowed to see it
- Freshness and row-count checks on each source, so a system that stops sending is noticed before a dashboard goes quiet
Clients we have done this for
Manufacturing
A governed Databricks lakehouse that joins Business Central with the scale house, the line historian, the lab and market prices, with nine leadership dashboards and a Genie space, plus Dext expenses posting into Business Central without re-keying.
B2B ecommerce
AmTab
Orders placed on amtab.com reach Business Central without anyone re-keying them. Power Automate keeps the store, the CRM and the ERP holding the same records, and the sales team turns a quote into an order in the system that invoices it.
Warehouse management
Funko
A warehouse management system built to cut operating expense, reduce reliance on manual work, and double throughput efficiency.
Where this goes next
Dynamics 365 and Business Central
If the ERP itself needs implementing or fixing first
Data engineering
If the data has already landed and the pipelines are the problem
Unity Catalog consulting
Governance for the tables once they arrive
Business Central reporting: built-in, Power BI or lakehouse
Which layer a Business Central reporting problem actually needs
Business Central's MCP server and data queries
Agents querying Business Central directly, and where the lakehouse takes over
AI assistants and enterprise search
What people build on the data once it's in one governed place
FAQ
Data integration: common questions
What are data integration services?
Getting data out of the systems a business runs on and into one place where it can be joined, governed and trusted. For us that place is Databricks. The work is deciding how each source is read, building the pipelines that keep it current, and resolving the records that don't match from one system to the next.
Does Databricks have a connector for Business Central?
No. Lakeflow Connect's Dynamics 365 connector reads data that Azure Synapse Link exports from Dataverse, and Business Central doesn't store its data in Dataverse.
Two routes work: a Databricks job reading the Business Central API pages incrementally on lastModifiedDateTime, or the bc2adls extension exporting tables to Azure Data Lake Storage for Databricks to read. Microsoft archived its own bc2adls repository in September 2023, and the community fork is the one still released.
Can you connect Salesforce or HubSpot to Databricks?
Yes. Both have managed connectors in Lakeflow Connect, so ingestion is configuration and the effort moves to what comes after it: matching CRM accounts to ERP customers, deciding which CRM fields anyone trusts, and setting who can see pipeline and revenue.
HubSpot's connector only authorises through a browser OAuth flow, so someone who can sign in to HubSpot has to be there when the connection is created.
When is a managed connector the wrong choice?
When it doesn't cover the source, when you need a table or field it doesn't expose, or when the source only drops files.
The Dynamics 365 connector, for instance, takes at most 250 tables per pipeline and doesn't follow a column's data type change on its own. We read those limits for each source before we put a date on anything.
What does a finished integration look like?
One we've published is a manufacturing plant in its first year. Business Central was joined with the scale house, the line historian, the lab and market prices: seven sources feeding 12 bronze, 15 silver and 10 gold tables, behind nine leadership dashboards and a Genie space.
One report matches every Business Central receipt to its scale ticket, which neither system could do alone.
Is this the same as connecting the systems to each other?
Not quite. Landing data in Databricks serves reporting, analytics and AI. Keeping operational systems in step, so an order placed on a website reaches the ERP without anyone re-keying it, is a separate job, and we do that too. For AmTab, Power Automate keeps the store, the CRM and Business Central holding the same orders, customers and invoices.
The rest of databricks
Databricks consulting
Data and engineering leaders choosing a Databricks partner
Hire Databricks engineers
Engineering and data leaders who need Databricks capacity quickly
Lakebase implementation
Data and product leaders putting an operational workload on Databricks
Unity Catalog consulting
Platform and security leads who have to defend the setup to somebody else
Databricks cost optimization
Data platform leads whose Databricks bill is outgrowing the work