Portmux is a SAP to NetSuite migration service that moves your General Ledger, AR, AP, fixed assets, materials, and Sales orders out of SAP ECC or S/4HANA into NetSuite OneWorld with full multi-subsidiary, multi-currency fidelity.
SAP-to-NetSuite is one of the most demanding migrations there is, SAP's data model is broad (Financial Accounting, Controlling, Materials Management, Sales & Distribution, Production Planning, all interconnected) and its tables (BKPF, BSEG, MARA, KNA1, LFA1) require deep ABAP knowledge to query well. We bring the SAP-side expertise so the NetSuite side gets clean data with valid posting, reconciled balances, and an audit trail your finance team trusts.
SAP G/L Accounts (table SKA1/SKB1) mapped to NetSuite Chart of Accounts with Account Groups translated to NetSuite Account Types and account numbering preserved.
SAP Customer Master data migrated to NetSuite Customers with credit limits, payment terms, billing/shipping addresses, and one-time customers handled separately.
SAP Vendor Master data migrated to NetSuite Vendors with payment terms, default expense accounts, 1099 status, and W-9 attachments.
SAP Material Master records migrated to NetSuite Items with material type translation (FERT → Assembly, ROH → Inventory, HALB → Sub-Assembly), default sales/purchase accounts, and current stock.
SAP Bills of Material flattened to NetSuite Assembly Item BOMs; multi-level BOMs preserved with parent-child relationships and routing data captured as NetSuite custom records.
SAP Cost Centers and Profit Centers mapped to NetSuite Departments, Classes, or custom segments depending on your reporting needs.
Open and historical SAP Sales Orders migrated to NetSuite Sales Orders with line items, pricing conditions flattened, and delivery/billing status preserved.
Open and historical SAP Purchase Orders migrated to NetSuite Purchase Orders with line items, expected receipt dates, and vendor invoice receipt status.
SAP Customer Invoices (table BKPF/BSEG document type RV) migrated as NetSuite Invoices; Vendor Invoices (document type RE) migrated as NetSuite Vendor Bills with applied payment history.
SAP Journal Entries (BKPF/BSEG with manual posting types) migrated to NetSuite Journal Entries; auto-generated posting from delivery/invoice consolidated as opening balance JEs.
SAP Asset Accounting (FI-AA) data migrated to NetSuite Fixed Assets Management with original cost, accumulated depreciation, useful life, and depreciation schedule.
SAP Company Codes mapped to NetSuite Subsidiaries (OneWorld); intercompany accounts and elimination entries preserved for consolidation.
We connect to SAP via direct database read replica access (preferred) or via SAP's RFC/BAPI interfaces with appropriate authorization objects. The data extraction pulls from BKPF/BSEG (FI documents), KNA1/LFA1 (customer/vendor master), MARA/MARC (materials), and module-specific tables. Within 2 weeks you see a complete data inventory across all in-scope modules and a Cost Center / Profit Center mapping proposal for NetSuite.
Mapping is the longest phase: COA mapping (with your CFO), Cost Center/Profit Center to NetSuite Class/Department/Custom Segment, Material type translation, Customer/Vendor consolidation (SAP often has duplicates), and pricing condition flattening. NetSuite Sandbox loaded with COA + master data first for finance team validation before any transactions are loaded.
Migration runs in waves: Master data (customers, vendors, items) first, then opening balances at cutover date, then historical transactions (typically 3–7 years). Each wave is reconciled to SAP source totals before the next wave starts. On cutover day, SAP is set to read-only, NetSuite goes live, and a final delta of post-cutover SAP transactions (typically <50) is migrated.
Every migration has its own gotchas. Here's what we plan for on this specific path.
SAP's data model is documented but vast. Pulling clean data from BKPF (header) + BSEG (line items) for FI documents requires understanding posting keys, special G/L indicators, and document types. We use direct database access where available, or a BAPI-based approach with explicit document type filters. ECC vs S/4HANA tables differ slightly, we handle both.
SAP Company Codes have intercompany accounts, elimination entries, and group consolidation logic. NetSuite OneWorld supports the same concepts (Subsidiaries with intercompany) but the elimination logic is different. We design the NetSuite Subsidiary structure to preserve consolidated reporting, with explicit handling of intercompany clearing accounts.
SAP Bills of Material support multi-level BOMs with phantom assemblies, alternative BOMs, and routing data. NetSuite Assembly Items support multi-level BOMs but with simpler routing modeling. We flatten or split BOMs as needed and document each manufacturing flow that lost structure for review by your operations team.
SAP SD pricing uses condition records (KONV, KONP) with complex hierarchies (customer-specific, material-specific, time-bound). NetSuite uses Item Pricing with Customer-specific overrides. We flatten the most-used pricing scenarios into NetSuite price levels and document edge cases that need manual handling.
Single-system migrations like SAP to NetSuite run as Track A engagements: one source, one destination, up to 1M records, 4–6 weeks. Final price depends on object volume, custom field count, and integrations, scoped on a 20-minute call before any commitment. See full pricing →
Tell us what's in the source, where it's going, SaaS or custom, and when you need to be live. You'll walk away with a scoped quote, a named engineer, and a go-live date.