Migrate from Wiise to Infor CloudSuite Corporate

Wiise Customer master records (name, address, contact details, payment terms, credit limits) map directly to Infor CloudSuite Customer. We resolve the Customer Number and any dimensional cost-centre or location tags attached to the customer record. Custom Fields on the Customer card migrate to Infor OS custom attributes; note the 2-decimal limitation on any decimal-type custom fields in Wiise and flag precision loss during pre-flight mapping.

Wiise Vendor cards map to Infor CloudSuite Supplier. Purchase terms, currency settings, and any vendor-specific dimensional tags migrate directly. Like Customer, Custom Fields on the Vendor card carry the 2-decimal precision limitation for any decimal values and are flagged in the mapping report before import.

Wiise Items (stock items, non-stock items, and services) map to Infor Item master with unit cost, inventory posting groups, and warehouse location assignments. Item-specific custom fields are subject to the same 2-decimal precision rounding as Customer and Vendor custom fields. We confirm the destination warehouse locations exist in Infor before importing item-location quantity records.

Wiise uses a dimensional Chart of Accounts with cost-centre, department, and location tags attached to every posting. Account codes and names migrate directly, but dimensional assignments require explicit field-level mapping to Infor dimension sets. We audit the Wiise dimensional usage before mapping, flag any dimensions used across entities that may need clarification on entity ownership, and configure Infor dimension sets before any transaction import begins.

Outstanding purchase invoices and sales invoices migrate as open records preserving invoice date, due date, remaining amount, and currency. We capture full invoice line history on request but note that the most recent trial balance should be captured as an opening balance reference point in Infor. Dimensional tags on open transaction lines require the same dimension-set mapping as the Chart of Accounts.

Fixed Asset records (acquisition date, cost, depreciation method, book value, location) migrate directly. We preserve depreciation schedules as-is and flag any assets still under depreciation at the migration date so that Infor's depreciation run picks up from the correct book value. Fixed Asset location maps to an Infor dimension or site code.

Wiise Jobs support task-level work breakdown, resource assignments, and billing. We map Job headers and tasks directly. Job-specific dimensional tags migrate as custom fields in Infor to avoid schema conflicts where the destination Project module uses a different dimensional framework. Resource assignments require the corresponding Infor work centre or cost pool to exist before import.

Employee records (name, position, department, employment status, HR metadata) migrate for both active and terminated employees. Effectivity dates and employment status map to Infor's date-effective HR structure, which may require field-level adjustment depending on the Infor HCM edition in use. We scope employee records as a distinct migration workstream and recommend HR team sign-off before import.

Wiise Payroll is a priced add-on per active employee with schema tightly coupled to Australian and New Zealand compliance requirements. Pay runs, superannuation contributions, and leave balances require explicit migration as a separate data set from core employee records. We scope payroll as its own workstream, flag any fields that cannot map directly to the destination HR or payroll system, and recommend finance and HR joint sign-off before any payroll data loads.

Bill of Materials, production orders, and routing headers are standard objects available on Wiise Premium. We map BOM line items, quantities per assembly, and routing work-centre assignments directly. Material costs carry the same 2-decimal rounding limitation as Item custom fields. We confirm the Infor work-centre and operation sequence codes exist before importing routing data, and flag any BOMs with linked dimensional tags for separate dimensional mapping.

Wiise does not expose a public API endpoint for document and attachment retrieval. Binary files (invoices, purchase orders, images) cannot be extracted programmatically. We scope document export as a manual pre-cutover step using Wiise's built-in export function, and we deliver a document-to-record mapping spreadsheet so that each file can be reattached manually to the corresponding Infor Customer, Supplier, or Transaction record post-migration. This manual step must be priced and scoped separately.

Wiise's single-subscription multi-entity model means all company entities share a database but are logically separate. We export each entity's books as a separate company unit and include intercompany balancing entries. In Infor CloudSuite, each entity becomes its own tenant with intercompany trading configured through ION or Infor OS workflows. We scope each entity as a distinct migration unit and resolve intercompany entry dimensional tags across entity boundaries before import.