Migrate from INNERGY ERP to Acumatica

INNERGY customer records map directly to Acumatica Customers. Name, email, phone, address, and industry map as direct field mappings. Multi-contact customer records in INNERGY may require Acumatica Contact sub-records or integration with Acumatica's CRM module depending on your Acumatica edition configuration.

INNERGY project and job records map to Acumatica Opportunities (or Project Management tasks if your Acumatica edition includes the Project module). Project name becomes Opportunity Name. Project amount maps to Amount. Stage/status maps to Opportunity Stage Name via value mapping. Project start and target dates map to CloseDate or custom date fields.

INNERGY's production scheduling data — shop start dates, milestone dates, workstation assignments — has no native Acumatica equivalent. We map these to custom datetime and text fields on Opportunity and create a custom Project Task structure in Acumatica to replicate the production timeline view. Your team configures the scheduling UI in Acumatica post-migration.

INNERGY's Bottleneck Report identifies production constraints per job. This data migrates as custom fields (Bottleneck_Station__c, Bottleneck_Date__c, Capacity_Constraint__c) on the Opportunity. We also create a supplemental custom table in Acumatica for historical bottleneck records. Reporting continuity requires Acumatica Report Designer or a BI tool to replicate INNERGY's bottleneck visualization.

INNERGY's throughput tracking (monthly plan vs. actual progress) has no direct Acumatica equivalent. We map historical throughput records to a custom Throughput_History__c table in Acumatica linked to Opportunities. New throughput tracking workflows must be rebuilt using Acumatica's screen-based processes or custom pages.

INNERGY stores finish type, hardware specifications, material grade, edge banding, and other millwork-specific attributes. These map to Acumatica user-defined fields (UDFs) created via Customization Project editor. Field naming uses the Usr prefix (e.g., UsrFinishType, UsrHardwareSpec). Acumatica stores UDF values in CSAnswers — the migration maps INNERGY property values to the corresponding UDF entries per Opportunity.

INNERGY BOM data for custom millwork components maps to Acumatica Non-Stock Items (if using Distribution Edition) or Inventory Items with BOM structures (if using Manufacturing Edition). Complex ETO BOMs with multiple revision levels require Acumatica's BOM revision tracking and may need manual reconciliation by your Acumatica manufacturing consultant.

INNERGY vendor records map directly to Acumatica Vendors. Name, contact info, payment terms, and account numbers map as direct field mappings. INNERGY vendor catalogs may require supplementary mapping if they contain material-specific pricing that feeds into Acumatica's vendor pricing schemes.

INNERGY purchase orders map directly to Acumatica Purchase Orders. PO number, vendor reference, line items (inventory or non-stock), quantities, unit prices, and expected delivery dates map as direct field mappings. Open versus closed status is preserved to maintain the current operational state. Historical closed POs migrate with full line-item detail including material descriptions, quantities fulfilled, and totals paid to support audit continuity and historical reporting in Acumatica.

INNERGY work orders represent shop-floor job assignments. Acumatica has no native work-order entity — these map to Project Tasks (if Project Management is enabled) or to a custom work-order structure created via Acumatica's Customization Platform. Work order status, assigned workstation, and labor hours map to custom fields on the task.

INNERGY's estimating workflow generates quotes with material costs, labor rates, and markups. These map to Opportunity custom fields (Estimate_Total__c, Material_Cost__c, Labor_Cost__c) and line-item details stored as notes or a custom estimate detail table. The estimating UI itself must be rebuilt in Acumatica's screen framework or via a custom page.

INNERGY user and owner records are matched to Acumatica Users by email address. Unmatched INNERGY users are flagged before migration — your team either creates Acumatica user accounts first or assigns those records to a fallback Acumatica user. INNERGY role and permission data has no Acumatica equivalent and must be rebuilt using Acumatica's screen-level security model.

INNERGY file attachments on projects, customers, or work orders are extracted and re-uploaded to Acumatica's Note/Attachment entity linked to the corresponding record. File size limits apply (Acumatica default 25MB per file). Inline images in notes are extracted and re-hosted. Folder structure from INNERGY is preserved as a custom text field for reference.