At Kitepipe, we do a lot of integration with NetSuite. Many of our customers are high growth consumer, tech or biotechs with multi-currency operations, and NetSuite has the accounting features and extensibility that these firms need. Boomi tells us that NetSuite is the most commonly used connector in the Boomi ecosystem, and our experience supports this.
So, lots of you out there want to build integration processes to NetSuite! In this article we will survey the several ways to connect to NetSuite and provide some tips and guidelines from our NetSuite integration eBook.
You can download the full e-Book Advanced NetSuite Integration with Boomi and Kitepipe.
The average enterprise has 30+ approved cloud platforms – everything from eCommerce to CRM - everything transactional that happens in these systems needs to get posted into NetSuite.
As the place where revenue gets recognized, orders and shipments must be posted to NetSuite.
You may have an HRIS system, but the spend impact - payroll and expenses, must post to NetSuite.
NetSuite has a complete set of modules, but most enterprises choose additional applications that are optimized for a particular business function - these need integration!
Here is a chart showing how a typical B-to-B enterprise might use Boomi Netsuite integration to connect the organization for sales, fulfillment, supply chain and analytics. The Netsuite Shopify 3PL triangle is a common Boomi integration project for Kitepipe. Netsuite to AWS data stores are an increasingly common Boomi use case. Concur for expense and vendor management is frequently chosen by Netsuite customers.
There are a several ways to get data in and out of NetSuite using Boomi - here is a summary of the approaches:
NetSuite API – Standard NetSuite API, used by the Boomi NetSuite connector; provides both query and create/update methods, and access to all standard and custom objects and fields.
Pros: Access anything in NetSuite; Both Get and Post; Standard and custom objects; query capability. Cons: Limits to multi-table joins; Performance issues with large queries.
Pros: access powerful saved search join and filter logic; Cons: limitations on access to some object types, performance issues for large queries.
Pros: Supports SQL-like access to NetSuite data model; Good for high volume extracts. Cons: Complexity in navigating NS data model, differences in field naming; Requires Suite Analytics licensing thru NetSuite.
Pros: design and implement custom API running in NetSuite; manage complex integration updates in NetSuite; Cons: Requires NetSuite development and scripting skills.
Pros: Use comprehensive saved search functionality; runs search and file dump with good performance; Cons: Requires install and management of NetSuite Script to run Saved search, convert to CSV, and Push to File cabinet.