Migrate from Perfecto ERP to Infor CloudSuite Corporate

Perfecto ERP's multi-level hierarchical account structures map to CloudSuite's Chart of Accounts with parent-child relationships preserved. We map each account level and flag any accounts that exceed CloudSuite's maximum hierarchy depth. UTF-8 encoding is verified during CSV conversion from Excel exports. Account type (Asset, Liability, Equity, Revenue, Expense) maps to CloudSuite account classification codes.

General Ledger transactions migrate as journal entry records with date, account reference, amount, and description preserved. Journal entry numbering sequences transfer to CloudSuite's journal entry numbering scheme. We flag any journal entries with unbalanced debits and credits before load to prevent import rejection. Post-approval General Ledger entries (closed periods) migrate with a posted status flag; open period entries require accounting-period validation in CloudSuite before migration.

Customer records from Perfecto ERP's Financial Package map to CloudSuite Customer records. Standard fields (name, contact, address, payment terms, tax registration) migrate 1:1. Any End-User Customization Studio fields on Customer records are identified during discovery and mapped to CloudSuite custom fields created before migration. Customer payment terms map to CloudSuite payment term codes.

Vendor records follow the same structure as customer records and migrate with vendor-specific fields (tax registration, payment terms, bank details) preserved. We flag any vendors with duplicate tax IDs or incomplete addresses before import to avoid CloudSuite validation failures. Vendor-specific fields from End-User Customization Studio transfer to CloudSuite custom fields.

Items include finished goods, raw materials, and services. We map item codes, descriptions, unit of measure, and cost prices directly. Item type (stock, non-stock, service) maps to CloudSuite item type codes. Any custom fields added via End-User Customization Studio are discovered during scoping and created in CloudSuite before item migration begins.

BOM relationships in Perfecto ERP's Supply Chain Package create dependencies between parent Items and component Items. Parent items must migrate and receive CloudSuite Item IDs before component items can be imported, because BOM component records reference the parent's ID. We run BOM migration as a separate pass after the main Items migration, validate referential integrity after load, and flag any orphaned components that reference Item IDs not found in the destination. Multi-level BOMs (sub-assemblies) require cascading resolution across multiple passes.

Employee profiles migrate with standard HR fields (name, employee ID, department, position, hire date). We preserve role-based security assignments by mapping Perfecto ERP role names to corresponding CloudSuite security groups during migration. Employee records import before role assignments so that the security group-to-employee mapping resolves correctly.

Role-based security from Perfecto ERP is extracted as a role-permission matrix and mapped to CloudSuite security groups with module-level and field-level access control. We do not migrate role configurations as live settings; we deliver a written role-permission mapping document listing each Perfecto ERP role, its permissions, and the equivalent CloudSuite security group and field access configuration for the customer's administrator to implement. Permissions that have no CloudSuite equivalent are flagged for review.

Purchase orders, sales orders, and inventory transactions migrate with transaction dates and line-item relationships preserved. Open transactions are prioritized for migration with a defined cutover date; closed transactions migrate as historical records. We validate that PO and SO line items reference valid Item IDs in CloudSuite before import. Transaction totals are reconciled against Perfecto ERP reports before final commit.

Approval Workflows define custom approval chains tied to specific transaction types. These do not migrate as live configurations because workflow engines differ between Perfecto ERP and CloudSuite. We extract workflow definitions (trigger conditions, approver chains, escalation rules) as a written configuration inventory document. The customer's Infor administrator rebuilds these in CloudSuite's workflow designer using the delivered inventory as the specification. Approval rules that are purely data-driven (e.g., amount thresholds) may be configurable in CloudSuite without custom code.

File attachments stored in Perfecto ERP export as files to a neutral store (network share or cloud storage) with a reference mapping file listing the source record, file name, and destination path. Post-import, we relink files in CloudSuite's Infor Document Management (IDM) module or as ContentDocument records attached to the parent record. Attachment storage paths are not portable between systems, so this is a two-step export-then-relink process.

End-User Customization Studio allows customers to add custom fields to standard objects without developer intervention. These fields are visible in the Perfecto ERP UI but may not appear in default Excel exports. During discovery, we identify all custom fields per object, request extended Excel exports that include custom columns, and create matching custom fields in CloudSuite before data migration begins. Fields with no clear CloudSuite equivalent are flagged for the customer to prioritize for rebuild or retirement.