Migrate your Wiise data

Customer master records are standard objects with name, address, contact details, payment terms, and credit limits. We map 1:1 to the destination Customer/Account schema. Custom Fields on Customer cards (up to 4 text, 2 lookup, 2 date) are preserved as additional attributes in the migration record.

Vendor cards follow the same structure as Customers. We migrate all vendor master data including purchase terms, currency settings, and Custom Fields. Vendor-specific dimensional tags for cost-centre allocation are carried forward as custom properties in the target system.

Items cover inventory stock items, non-stock items, and services. We map Item unit cost, inventory posting groups, and warehouse location assignments. The 2 decimal-place limitation on Item custom fields is honoured — values beyond 2 decimal places are rounded during import with a warning flag raised in the mapping report.

Wiise uses a dimensional chart with cost-centre, department, and location tags attached to every posting. Account codes and names migrate directly, but dimensional assignments require field-level mapping to match the destination's dimensional structure, which varies significantly between ERP platforms.

Outstanding purchase invoices and sales invoices are migrated as open records. We preserve invoice date, due date, remaining amount, and currency. Full invoice line history is migrated on request but requires explicit scoping — customers who skip this step end up with balance-only records in the new system.

Wiise Jobs support task-level work breakdown, resource assignments, and billing. We map Job headers and tasks directly. Job-specific dimensions are migrated as custom fields to avoid schema conflicts when the destination uses a different project model.

Employee records include name, position, department, employment status, and HR metadata. We handle both active and historical (terminated) employees. Where the destination HRMS uses different effective-dating conventions, we append an Effective_Date property to indicate the record's timeline position.

Fixed Asset records include acquisition date, cost, depreciation method, book value, and location. We preserve depreciation schedules as-is and flag any assets still under depreciation at migration date so the destination can continue the schedule without recalculating.

Wiise allows custom fields on 15 page types including Customer, Vendor, Item, Sales Header/Lines, Purchase Header/Lines, Job, Contact, Fixed Asset, Service Item, and production objects. We extract and carry all custom field values forward but note that lookup field options (unlimited) may not have equivalents in the destination system — these are migrated as plain-text values with a mapping note.

Wiise does not expose a public API endpoint for document and attachment retrieval in its standard offering. Binary attachments (invoices, purchase orders, images) cannot be reliably extracted via documented API calls. We recommend customers export these manually through Wiise's UI export function before migration and re-upload to the destination separately.

Wiise supports managing multiple legal entities under one subscription with intercompany transactions. We export each entity's books as a separate company unit and include intercompany balancing entries. The destination must be able to represent multi-entity relationships — if it cannot, we consolidate into a single entity with entity-code prefixes on all account codes.

Multiple warehouse locations are supported and each inventory item can have bin-level quantity records per location. We migrate item-location quantity records directly. Where the destination uses a simpler single-location model, we sum quantities and flag multi-location items in the summary report.

Payroll is a priced add-on module. Employee compensation history, pay runs, and superannuation contributions can be migrated, but the Wiise payroll schema is closely tied to Australian and New Zealand compliance requirements. We recommend payroll migration as a separate workstream with HR and finance sign-off on each record class before import.

Available on Premium tier. Bill of Materials, production orders, and routing headers are standard objects. We map BOM line items, quantities per assembly, and routing work-centre assignments. Material Requirements Planning (MRP) suggestions are not migrated as they are computed dynamically by the system.