Migrate from Wiise to Epicor Prophet 21

Wiise Customer cards map to Epicor Customer with name, address, contact details, payment terms, and currency settings transferred directly. We resolve the CustomerShpTo (ship-to address) records as Epicor ShipTo records attached to the same CustomerNum. Credit limits and payment terms become Epicor CashTerms and CreditLimit fields. Multi-currency settings on the Wiise customer card migrate to the Epicor Customer Currency record.

Wiise Vendor cards map to Epicor Vendor with the same structure as Customer. Purchase terms, currency settings, and payment methods transfer to Epicor Vendor records. Where Wiise vendor cards carry cost-centre dimensional tags for AP posting, we map these to Epicor VendorPPGroup (Posting Price Group) for PO routing and apply cost-code defaults during AP invoice entry.

Wiise Items (stock, non-stock, and service) map to Epicor Part records. Item type, inventory posting groups, and warehouse location assignments transfer to Epicor's Part with TypeCode (Stock, Non-Stock, Service), PartClass, and PartWhse records. Wiise's 2 decimal-place limit on custom Item fields means any decimal precision above 2 places is rounded before Epicor import; we flag every instance in the pre-flight mapping report.

Wiise uses a dimensional chart with cost-centre, department, and location tags on every posting. We map Wiise account codes to Epicor GL Account numbers directly and map the dimensional tags to Epicor Cost Codes. During scoping, we verify that the Epicor Cost Code structure (which can be up to 20 characters and hierarchical) accommodates the full set of Wiise dimension combinations. Any unmatched dimension combinations are escalated before the first GL import.

Outstanding AP and AR records migrate as open Epicor APInvoiceHed and ARInvoiceHed entries with invoice date, due date, remaining amount, and currency preserved. We use Epicor'sAPInvoice or ARInvoice endpoints to insert header and detail lines. Invoice totals are reconciled against the Wiise trial balance before the import phase opens. Lines referencing inventory items require a matching Part record to exist in Epicor first, so we stage Parts before AP/AR.

Wiise BOMs (Premium tier) map to Epicor PartBill with the parent Part as the finished good and BOM lines as PartMtl entries with quantity-per-assembly and scrap percentages. Wiise BOM revision numbers map to Epicor RevisionNum with an effective date preserved. Routing headers (Premium tier) map to Epicor JobOper records with work-centre assignments, cycle times, and setup hours. We verify that the Epicor site ID exists for each BOM before import because BOMs in Epicor are site-specific.

Wiise Jobs with task-level work breakdown, resource assignments, and billing map to Epicor Project and ProjectPhase records. Job-specific cost dimensions from Wiise migrate as Epicor WBS codes or Cost Codes on the Project. Epicor's Project Control module supports milestone billing, progress billing, and job costing against a budget, which is more sophisticated than Wiise's job-costing model; we preserve Wiise job totals as opening values on Epicor Project Phase budget fields.

Wiise Fixed Asset records (acquisition date, cost, depreciation method, book value, location) map to Epicor FAAsset with the depreciation schedule preserved as-is. We flag any assets still under depreciation at migration date so that the customer can set the correct fiscal year start for depreciation posting in Epicor. Asset disposals and revaluations from Wiise migrate as adjustment transactions against the existing Asset record.

Wiise Employee records (name, position, department, employment status, HR metadata) migrate to Epicor Employee with active and terminated employees included. Wiise payroll history (pay runs, superannuation, leave balances) is in a separate priced add-on module and migrates as a distinct workstream; we recommend HR team sign-off on employee-level records and coordinate with the customer's chosen payroll destination. Epicor's HR module uses an EmployeeNum as the primary key; we resolve by personal email as the dedupe match.

Wiise warehouse locations with bin-level item quantities map to Epicor Plant (Site) and Warehouse records with bin locations preserved as PartBin entries. Where Wiise uses location codes for inter-company transfers, we map these to Epicor Site codes and verify that the inter-company trading setup in Epicor is configured to match the Wiise multi-entity structure before inventory quantities transfer.

Wiise custom fields on Customer, Vendor, Item, Sales Header/Lines, Purchase Header/Lines, Job, Contact, Fixed Asset, and Service Item migrate to Epicor UD fields (UD01-UD30 tables) or as custom fields on the relevant Epicor table. We pre-create the UD schema in Epicor before data migration, matching Wiise field types (text, lookup, date, decimal) to the equivalent Epicor data type. The 2 decimal-place limit on Wiise custom decimals carries forward as-is; we flag precision rounding in the pre-flight report.

Wiise has no public API endpoint for binary attachments. We advise customers to use Wiise's built-in export function to download attached documents (invoices, POs, scanned files) before the cutover date and store them in a shared location for manual upload to Epicor DMS post-migration. Epicor's document management is available with full CRUD API, but binary files must be uploaded separately from structured data in this migration pattern.

Wiise Payroll is a priced add-on calculated per active employee and stores pay runs, superannuation, and leave balances in a schema tied to Australian and New Zealand payroll compliance. We extract employee compensation history and leave balances as a structured export, but the Wiise payroll schema is not a standard Business Central table and requires a separate migration run into an external HRMS or the customer's chosen payroll platform. HR team sign-off is required before any employee record crosses into Epicor.