Forum Discussion
Netsuite connector for Fabric
Hi Rocky1001,
Currently, Microsoft Fabric does not offer a native connector for NetSuite. Commonly used approaches include:
CData Sync -- OneLake (Parquet/Delta):
This is a cost-effective solution compared to fully managed ELT, supporting incremental replication and flexible scheduling. However, it requires some operational management as you will be running the service.Fivetran -- OneLake (Delta):
This fully managed option delivers data directly into OneLake with minimal setup. Most objects support incremental loads, though some tables may need full refreshes periodically. It is the lowest-maintenance approach but comes at a higher cost.DIY solutions (SuiteAnalytics ODBC/JDBC or REST/SuiteQL APIs):
These can be integrated through Fabric pipelines or notebooks, but you will need to develop and maintain your own incremental logic, as well as manage authentication, pagination, and throttling.For smaller data volumes, CData Sync into OneLake offers a good balance between cost and effort. If budget allows and a fully managed solution is preferred, Fivetran → OneLake is the most straightforward option.
Thank you.
Resolver IMS Fabric does not have Netsuite native connector for extracting data into Fabric. As pointed out by you, CData is lower cost when comparte to Fivetran.
Use Cdata Sync -> Netsuite -> Onelake (parquet file) in Fabric lakehouse
or
use Rest API to connect Netsuite and load into Fabric lakehouse using spark notebook.
Hi, thanks for the message, yes the the 2 options I've narrowed down is CData if using a mamanged option or using the customer ODBC option, I was just wondering if there are any other better options I'm not aware of that people are using 🙂
v-sgandrathiCommunity Support
Hi Rocky1001,
Currently, Microsoft Fabric does not offer a native connector for NetSuite. Commonly used approaches include:
CData Sync -- OneLake (Parquet/Delta):
This is a cost-effective solution compared to fully managed ELT, supporting incremental replication and flexible scheduling. However, it requires some operational management as you will be running the service.Fivetran -- OneLake (Delta):
This fully managed option delivers data directly into OneLake with minimal setup. Most objects support incremental loads, though some tables may need full refreshes periodically. It is the lowest-maintenance approach but comes at a higher cost.DIY solutions (SuiteAnalytics ODBC/JDBC or REST/SuiteQL APIs):
These can be integrated through Fabric pipelines or notebooks, but you will need to develop and maintain your own incremental logic, as well as manage authentication, pagination, and throttling.For smaller data volumes, CData Sync into OneLake offers a good balance between cost and effort. If budget allows and a fully managed solution is preferred, Fivetran → OneLake is the most straightforward option.
Thank you.
- v-sgandrathi
Hi Rocky1001,
Just wanted to follow up and confirm that everything has been going well on this. Please let me know if there’s anything from our end.
Please feel free to reach out Microsoft fabric community forum.
