Migrate from Exxas Cloud Business Platform to Infor CloudSuite Corporate

Exxas Central module stores person-level contacts with custom fields and multi-currency billing addresses. We map these to Infor's ContactPerson or global party model depending on the target CloudSuite edition. German honorifics (Herr/Frau) map to Infor's gender or title fields. Email addresses, phone numbers, and postal addresses migrate to Infor's party contact fields with ISO-formatted country codes. Any Exxas custom fields on contacts become Infor extended attributes on the party record.

Exxas company records map to Infor Customer or Supplier party records depending on the account type field. The Exxas company registration number and VAT ID migrate to Infor's tax registration fields. Infor requires that at least one active party address exists before transaction records can be linked; we ensure address completeness during the extract phase and flag any company record missing a primary address.

Exxas Sales deals map to Infor Opportunities for pre-close pipeline tracking, with stage names translated to Infor's Sales Stage values. Closed-won Exxas deals become Infor Sales Orders; closed-lost deals are held as a flagged Opportunity with a loss reason custom field. The Infor CloudSuite migration utility handles the opportunity-stage mapping, but we pre-configure the sales process and record type in Infor before loading.

Exxas deal line items map to Infor Sales Order or Purchase Order lines with product reference, quantity, and unit price. We resolve the Infor Product2 equivalent using Exxas product code as the dedupe key. If Exxas uses bundled or composite pricing that Infor handles differently, we split into component lines and flag for Infor admin review.

Exxas Service tickets map to Infor Service Management (if CloudSuite Service edition is licensed) or to a custom Case object. Ticket priority, status, and assignment relationships preserve. Attachment handling depends on Infor's document management configuration; we migrate attachments as content records if the target Infor tenant has Document Management enabled, or flag for manual post-migration attachment as a documented step.

Exxas project hierarchies with sprints, tasks, and Kanban boards map to Infor Project Management or Manufacturing Work Orders depending on whether the project is customer-facing or production. Employee assignments link to Infor HCM employee records via worker ID. Sprint burndown metrics do not transfer; Infor does not store sprint velocity as a native metric and teams typically recreate these in Infor's reporting layer post-migration.

Exxas product records with pricing tiers and stock-on-hand map to Infor Item masters with inventory attributes. BOM relationships migrate to Infor Bill of Materials linked to the finished item. Warehouse-specific bin locations require manual reconciliation because Exxas bin configuration does not have a direct Infor equivalent; we provide a warehouse mapping table as part of the handoff.

Exxas employee profiles with job titles, departments, employment start dates, and effective-date compensation history migrate to Infor HCM Worker records. Exxas country-specific benefits and Swiss social security identifiers migrate to Infor HCM extended fields. Historical pay rates migrate as read-only compensation records so that future Infor HCM payroll runs have reference data. We flag any employee record with missing required Infor HCM fields (legal name components, national ID) before import.

Exxas payroll run data is tightly coupled to Swiss statutory tax and social security calculation engines and does not migrate. Exxas payroll exports as read-only compensation history (effective-date pay rates, bonus records, deduction history) for reference in Infor HCM. Full payroll recomputation happens in Infor HCM's Swiss payroll module after go-live. This is disclosed upfront during scoping and is a non-negotiable limitation of this migration pair.

Exxas chart of accounts migrates to Infor Financial Management with account type mapping (asset, liability, equity, revenue, expense). Open AP and AR records migrate as open items with customer/vendor references, invoice numbers, due dates, and amounts in the functional currency. Historical closed periods migrate as read-only journal batches for audit and regulatory reference. The Infor migration database requires account structure to be seeded before transaction records load, so we sequence the chart of accounts first.

Exxas Marketing module stores campaign records with lead flows and lead assignments. Infor Cloudsuite ERP does not have a native marketing automation layer; campaigns from Exxas migrate as Infor CRM Campaign records for tracking reference, but lead scoring, lead nurturing, and campaign workflows do not transfer. We document the campaign list structure and suggest Infor Marketing Cloud or a third-party marketing automation tool if the customer requires continued campaign automation.