Migrate from Sage Intacct to Epicor Prophet 21

Sage Intacct GL accounts map to Epicor Kinetic chart of accounts entries with subaccount segmentation designed during scoping. Account number, name, type, and active status transfer directly. Sage Intacct's dimensional tagging does not map to an Epicor native equivalent—instead, we design Epicor subaccount segments (e.g., Department-Division-Cost Center) and map Sage dimension values into the appropriate segment positions, preserving filterable analysis capability. The mapping is validated in an Epicor test company before production import.

Historical journal entries migrate to Epicor GL Journal Entry records. Each journal entry line maps account number to the Epicor COA and applies the subaccount segment value derived from the Sage Intacct dimension assignment (department, class, location, or project). Entries in a 'posted' state migrate with post dates; entries in 'non-posted' or draft state are flagged in a reconciliation report for the customer's controller to post in Epicor before or after import. Non-dimensionalized GL transactions (Sage entries without dimension tags) migrate with a default subaccount value assigned at migration time.

Sage Intacct Dimensions (department, class, location, customer, project) are a unique tagging concept without a native Epicor equivalent. We do not migrate dimensions as an Epicor object because Epicor Kinetic does not have one. Instead, we map each dimension value to either an Epicor subaccount segment or a custom field on the GL Journal Entry record. The mapping is delivered as a written dimensional inventory document for the customer's Epicor administrator to configure in Reporting Categories and validate against existing reports before go-live.

Open Sage Intacct AP bills, payment records, and vendor associations migrate to Epicor AP Invoice Entry. We flag any Sage bills in 'pending approval' workflow state because Epicor requires AP approval configuration before invoices route. Vendor master records (addresses, payment terms, default expense accounts) map to Epicor Vendor records. Approval routing workflows do not migrate; we deliver an AP workflow configuration guide for the Epicor administrator.

Open Sage Intacct AR invoices, payment records, and customer records migrate to Epicor AR Invoice Entry and Customer master. Balance-forward vs open-item AR settings are assessed against the customer's source system configuration and mapped to Epicor's AR aging preference. Customer credit limits and payment terms transfer directly. Post-vs non-posted invoice handling mirrors AP: draft invoices are flagged for the controller to post before migration or re-create post-import.

Sage Intacct customer and vendor master records, including addresses, payment terms, default GL accounts, and contact information, migrate to Epicor Customer and Vendor records via Epicor REST API. Custom fields on these objects (stored with '!' prefix in Sage Intacct REST) require explicit field-level mapping to Epicor UD (User-Defined) fields. We discover all custom fields during schema mapping and apply the correct API naming convention before import.

Sage Intacct entity definitions, inter-company transaction rules, and consolidation mappings require explicit redesign in Epicor. Sage entities map to Epicor companies, but Epicor's inter-company journal entry setup uses a different configuration model (Inter-Company Journal Entry with sender and receiver companies). We deliver a written entity-to-company routing map for the Epicor administrator to configure post-migration. Cross-company elimination rules require manual setup in Epicor's consolidation module.

Sage Intacct project headers, task hierarchies, project status, billing type, customer association, and billable vs non-billable flags migrate to Epicor Project Management Entry or Epicor Kinetic Job records depending on the project's nature (service project vs manufacturing job). Project accounting dimensions (revenue recognition, grant tracking) are preserved as custom fields where Epicor's native project accounting does not cover the same scenarios. Project status and billing type require verification against the source system before migration.

Sage Intacct item records including description, unit price, cost, and GL associations migrate to Epicor Part Master records. Bundle and matrix items in Sage (parent-child relationships) map to Epicor Part Master with BOM (Bill of Materials) or Product Group structures. Unit of measure conversions require verification against Epicor's UOM setup because Sage and Epicor use different default UOM libraries.

Fixed asset records migrate but depreciation schedules require recalculation in Epicor ERP because each jurisdiction uses different conventions. We transfer acquisition cost, date, asset class, and accumulated depreciation from Sage Intacct. The customer's Epicor administrator reviews and activates the depreciation book configuration post-import. Assets in Sage that are fully depreciated or disposed require separate status flags set in Epicor.

Sage Intacct Planning module budget data migrates to Epicor Budget Entry records scoped to fiscal year and account. Epicor's budget scenario structure differs from Sage's Planning module scenarios; we map budget periods and amounts to the closest matching Epicor fiscal calendar. Budget approval workflows do not migrate; we deliver a budget workflow configuration guide.

Sage Intacct custom objects behave like database tables with fields that use '!' prefix in the REST API. These migrate to Epicor Kinetic custom tables created under Data Discipline. We pre-create the Epicor table schema including all custom fields, relationship definitions, and validation rules before any data import. The '!' field prefix naming convention is handled in our extraction scripts; Epicor table fields use standard naming without a prefix equivalent. Any relationship dependencies to standard Sage objects are resolved through our standard object mapping before custom object migration runs.

Custom fields on any standard Sage Intacct object (Customer, Vendor, GL Account, Invoice, Project) are discovered during schema mapping and mapped to Epicor UD fields on the equivalent object. The '!' prefix in Sage Intacct REST API is handled in extraction; Epicor UD fields are accessed via standard REST naming. We verify that the UD field data type in Epicor matches the source type (text, integer, date, currency, decimal) to prevent import rejection.

Document attachments stored within Sage Intacct are not accessible via REST API for bulk export. We do not migrate attachments as part of the record migration scope. We recommend a parallel document migration strategy (e.g., SFTP file transfer or Epicor EDMS configuration) alongside the record migration, managed separately by the customer's IT team.