Portmux is a Sage Intacct to NetSuite migration service that moves your General Ledger, AR, AP, and dimensional data (Department, Location, Class, Project, custom Dimensions) out of Sage Intacct into NetSuite with reconciled balances and a clean audit trail.
Sage Intacct and NetSuite are both multi-entity accounting platforms with strong dimensional reporting. The migration is rarely a downgrade, it's usually about consolidating onto NetSuite for an ERP-wide standardization (manufacturing, inventory, advanced revenue recognition). The work is in mapping Intacct's flexible Dimensions structure onto NetSuite's Subsidiary + Class + Department + Location + Custom Segments hierarchy.
Sage Intacct Chart of Accounts migrated to NetSuite COA with Account Type translation, account numbers preserved, and any account-level dimension restrictions documented.
Sage Intacct Customers migrated to NetSuite Customers with billing/shipping addresses, payment terms, default tax codes, customer-specific pricing tiers, and AR balances.
Vendor records with 1099 status, default expense accounts, payment terms, attached W-9s, and AP balances migrated to NetSuite Vendors.
Sage Intacct Items (Inventory, Non-Inventory, Service) migrated to NetSuite Items with default sales/purchase accounts, cost methods, and current quantity-on-hand.
Open and historical Sage Intacct AR Invoices migrated to NetSuite Invoices with line items, applied payments, sales tax, and Sales Order linkage flattened where Intacct used SO module.
AP Bills migrated to NetSuite Vendor Bills with expense and item lines, applied payment history, and bill credits applied against open balances.
Sage Intacct General Ledger Journal Entries migrated to NetSuite Journal Entries with original posting date, description, account splits, and dimensional tagging preserved.
Sage Intacct bank account histories migrated to NetSuite bank accounts with reconciled status, last-reconciled date, and historical transaction memos.
Sage Intacct standard Dimensions (Department, Location, Class, Project, Customer, Vendor, Employee, Item) and custom Dimensions mapped to NetSuite's segment structure.
Sage Intacct Entities (in multi-entity setups) mapped to NetSuite Subsidiaries with intercompany accounts and elimination entries preserved for OneWorld consolidation.
Active Sage Intacct Recurring Bills, Recurring Invoices, and Recurring JEs migrated to NetSuite Recurring Bills, Recurring Invoices, and Memorized Transactions.
Critical Sage Intacct Custom Reports rebuilt as NetSuite Saved Searches and Financial Reports with the dimensional rollups preserved.
We connect to Sage Intacct via Web Services API (XML SOAP) with a User Login that has Admin role and Web Services Subscription enabled. Intacct's API enumerates every Entity, COA account, Customer, Vendor, Item, Dimension, and historical transaction. Within 72 hours you see a complete inventory and a Dimension-to-NetSuite-segment mapping proposal.
Dimension mapping is the most important phase, Intacct's flexible Dimensions framework needs to map cleanly onto NetSuite's fixed segment hierarchy (Subsidiary + Class + Department + Location + up to multiple Custom Segments). Your controller approves the mapping. NetSuite Sandbox loaded with COA + Customer/Vendor/Item master data first for finance team validation.
NetSuite loaded with full Sage Intacct history. Trial balance, AR aging, AP aging, and bank balances reconciled to Intacct to the penny. On cutover day, Sage Intacct is set to read-only, NetSuite OneWorld becomes authoritative, and we run a final delta of post-cutover Intacct transactions.
Every migration has its own gotchas. Here's what we plan for on this specific path.
Sage Intacct allows unlimited custom Dimensions per transaction, organized however you want. NetSuite has fixed segments (Class, Department, Location, plus Custom Segments). We map Intacct standard Dimensions to NetSuite native segments and any Intacct custom Dimensions to NetSuite Custom Segments. If you have more than ~5 active custom Dimensions in Intacct, we may need to consolidate.
Sage Intacct's Projects module (with timesheets, expenses, billing) is feature-rich. NetSuite Projects (or NetSuite Project Management module if licensed) has overlapping but different functionality. We map Project records and historical project data, but project-driven workflows often need re-design in NetSuite, your project managers need 1–2 weeks of orientation.
Sage Intacct multi-Entity rolls up via Top Level entity with consolidation rules. NetSuite OneWorld uses elimination subsidiaries and consolidated reporting. Both work, but the mechanics differ. We design the NetSuite Subsidiary structure from your current Intacct Entity structure and validate consolidated financial statements before cutover.
If you use Intacct's Sales Order module, those records flow through Order → Invoice in Intacct. NetSuite Sales Orders work similarly but with stricter status workflow. We migrate open Sales Orders as NetSuite Sales Orders in their current status and historical SOs as reference; the SO → Invoice → Payment flow is re-validated with your AR team during rehearsal.
Single-system migrations like Sage Intacct 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.