Migrate from Prowess ERP to Infor CloudSuite Corporate

Prowess ERP's flexible Chart of Accounts with multi-entity Cost Centre hierarchies maps to Infor CloudSuite's Account Master structure. Every Prowess deployment has a different COA schema depending on the implementing partner's configuration, so we run a full schema inventory against the live database at the start of scoping. Account codes, descriptions, and Cost Centre assignments migrate as configured, with the original Prowess Cost Centre name preserved in a custom field for validation. Multi-entity consolidation structures in Prowess map to Infor's legal-entity or divisional account structures.

Prowess Customer records migrate to Infor CloudSuite Customer Master with name, address, contact details, and payment terms mapped 1:1. GST/Tax registration details stored as custom fields in Prowess map to the equivalent tax registration fields in Infor. Any custom customer properties added by the implementing partner require field-level mapping during the schema inventory phase. We flag vendor-specific credit limits and payment terms for manual confirmation after import.

Vendor master data migrates cleanly from Prowess ERP to Infor CloudSuite Vendor Master with standard fields (name, address, contact, GST registration, payment terms) preserved. Custom vendor-specific fields added during Prowess implementation require pre-import field mapping. We flag any vendor credit limits, tax registration numbers, and custom categories for manual confirmation post-import since these values often reflect partner-specific configurations that need Infor admin review.

Prowess Item Masters with manufacturing-specific attributes (BOM structures, work centres, unit-of-measure conversions) map to Infor CloudSuite Item Master. Standard fields (item code, description, uom, category) migrate 1:1. BOM and routing data are manufacturing-specific dependencies that we map as custom item-level attributes and flag for the customer's Infor admin to reconstruct in the BOM designer post-migration, since BOM structures have complex multi-level dependencies that require destination-context validation.

Outstanding payables and receivables require open-balance validation after migration. We extract the current balance, due date, and allocation status from Prowess and map to Infor CloudSuite's open invoice format. Any partially-allocated invoices require manual reconciliation by the finance team post-migration since allocation state is not always stored as a single field in Prowess and depends on the partner's implementation configuration.

Prowess ERP Purchase Order headers and line items transfer with status flags, quantities, pricing, and delivery dates preserved. Where Prowess uses custom workflow states not natively present in Infor CloudSuite, we map to the nearest equivalent state and flag records requiring state confirmation in the destination. PO approvals and holds are preserved as flags on the Infor Purchase Order record. Open POs in planning-stage versus execution-stage are distinguished by the order status and flag for downstream procurement workflow validation.

Sales Order headers and lines migrate with pricing, discounts, and fulfilment status intact. Custom fields added by the Prowess implementing partner require field-level mapping during schema inventory. Back-ordered lines and partial shipment flags are preserved and mapped to Infor's equivalent fulfilment status fields. Any Prowess-specific pricing tiers or customer-specific price lists are mapped to Infor's price book or customer-specific pricing structures.

Work order sequencing, BOM links, and routing data are manufacturing-specific and fully implementation-dependent in Prowess ERP. We preserve the work order header and line structure (order number, quantity, start/end dates, status, work centre assignment) and map BOM associations as item-level dependencies flagged for manual reconstruction in Infor's BOM designer. Routing data migrates as a custom attribute on the Job Order pending the customer's Infor admin review, since routing structures often require destination shop-floor configuration.

Owner and user assignments in Prowess ERP use internal IDs that differ by implementation. We resolve users by email address as the join key and map to Infor CloudSuite User records. Any orphaned assignments where a Prowess user has no matching Infor User go to a reconciliation queue for the customer's admin to provision before record import resumes. Employee records with manufacturing-specific roles (work centre operators, planners) require Infor role-based security review post-migration.

Every Prowess ERP deployment has a different custom field schema depending on the implementing partner's configuration work. We extract the complete Prowess schema at scoping time and map each custom field to its Infor CloudSuite equivalent, creating new custom fields in Infor where no standard equivalent exists. Custom field types (text, number, date, picklist, checkbox) are mapped to the corresponding Infor field type. Implementation-specific custom fields that reflect Prowess-only workflows are flagged for the customer to reassess whether they apply to Infor's operational model.

Binary document attachments stored in Prowess ERP's file system or blob storage are not accessible via a documented public API. We recommend a separate file-level migration using the implementing partner's file export capability, with documents ingested into Infor Document Management (IDM) post-migration. We provide a manifest of referenced document IDs from the Prowess database that the customer uses to coordinate the file transfer with the Prowess partner. This step is excluded from the standard migration scope.