The main cost drivers are whether you're syncing complex Salesforce CPQ configurations with NetSuite's pricing engine—especially when you've got custom price books, discount schedules, and approval workflows that need to map across both systems. Complexity really spikes when you're dealing with bi-directional syncs between Salesforce territories and NetSuite subsidiaries, or when your data volumes hit NetSuite's strict concurrency limits (15-55 concurrent requests depending on your tier) and you need sophisticated error handling for throttling.

Most implementations struggle with customer hierarchy mismatches—Salesforce's flexible account relationships don't map cleanly to NetSuite's rigid parent-child structure—and real-time opportunity-to-order flows that require custom RESTlets or Platform Events to work around API limitations.

Yes — OnePacific's integration approach is built around multi-subsidiary operations from day one. We map Salesforce Accounts to the correct NetSuite subsidiary based on your rules (region, entity, sales team, or custom logic), and we handle currency conversion so HKD, SGD, MYR, and other APAC currencies are correctly recorded against the right subsidiary. This is one of the most common failure points with off-the-shelf connectors — we handle it as standard.

At minimum: Accounts/Customers, Contacts, Opportunities to Sales Orders, and Invoices back to Salesforce. Most implementations also sync Quotes, Products/Items, Payment Status, and Fulfilment Updates. Bidirectional sync keeps customer and order records in both systems without re-entry. We map your specific Salesforce custom fields and NetSuite custom records as part of the scoping process — nothing is assumed.

Each order or invoice generated from a Salesforce opportunity is mapped to the correct NetSuite currency based on the customer's billing region. For APAC operations — whether you're running HKD, SGD, MYR, TWD, or AUD — we configure exchange rate rules and subsidiary routing so transactions hit the right books automatically. You don't need to manually convert or correct records post-sync.

Timeline typically ranges from 6–10 weeks depending on your data volumes, custom field mapping requirements, and the number of Salesforce objects in scope. Simpler deployments using pre-built Celigo flows can go live in 4–6 weeks. More complex implementations — especially those involving multi-subsidiary NetSuite OneWorld environments or high-volume order sync across APAC regions — usually take 8–12 weeks. We run a scoping session upfront to map your specific workflows before giving you a firm timeline.

Yes. We work with Salesforce CPQ for quote-to-order flows into NetSuite, Sales Cloud for opportunity and account sync, and Service Cloud for case-to-billing use cases. If you're running CPQ, we handle the Quote→Order→Invoice chain so approved quotes in Salesforce trigger sales orders in NetSuite automatically — no manual steps between teams.