The main cost drivers for SAP-NetSuite integrations are the complexity of mapping SAP's modular structure (like FI/CO modules) to NetSuite's unified data model, plus whether you need real-time or batch processing. Since there's no native connector, you'll need middleware like Boomi or Celigo, or custom development using SAP's Integration Suite with NetSuite's SuiteTalk APIs—and SuiteTalk's concurrency limits (15-55 concurrent requests) can force expensive workarounds for high-volume syncs.

Entity mapping gets particularly complex when SAP's material masters don't align with NetSuite's item records, and two-way syncs multiply the effort since you're dealing with SAP's document flow dependencies and period-end closing procedures that complicate cutover timing. Most companies underestimate the ongoing middleware costs and the data governance work needed to handle exception cases beyond the happy path.

SAP uses a cost center and profit center hierarchy that doesn't exist in NetSuite's segment structure. We build a mapping table that translates SAP GL accounts, cost centers, and profit centers into NetSuite accounts, classes, departments, and locations. The mapping is maintained in NetSuite as a custom record so your finance team can update it without touching code.

Conflict resolution rules are set per field during scoping. For example, SAP might own the billing address while NetSuite owns credit limits. If the same field gets updated in both systems between sync cycles, the designated source of truth wins and the other system's change is logged for review. You won't lose data, but you will know when a conflict happened.

Yes, and most companies do. The integration keeps master data, transactions, and GL balances synchronized between both ERPs while you migrate subsidiaries one at a time. Each entity gets turned off from the sync as it completes migration. Some companies run both systems permanently for different business units.

Both, depending on the data object. IDocs work well for master data distribution and transactional documents like purchase orders and invoices. BAPIs and RFC calls handle real-time lookups, like checking available stock or validating a customer number. We'll map which interface type makes sense for each integration point during scoping.

It depends on scope. A single-subsidiary migration with standard master data (customers, vendors, items, GL) usually takes 8 to 12 weeks from scoping to go-live. Multi-subsidiary rollouts can stretch to 6 months or longer if you're migrating entities in phases. The integration piece - keeping both systems in sync during the transition - adds 2 to 3 weeks of scoping on top of the core migration work.