Migrate from Exxas Cloud Business Platform to Epicor Prophet 21

Exxas Central holds person-level contact records with address, phone, email, and custom fields. We map these to Epicor Customer records of type Person. The Exxas contact's assigned Company link resolves to a separate Epicor Customer (Company) record created first. German-formatted addresses (Straße, PLZ, Ort) are normalized to structured address fields in Epicor during transform. Any Exxas custom fields on contact migrate to UD fields on the Customer table.

Exxas organizational company records map to Epicor Customer records of type Company. The Exxas company domain and industry vertical map to Epicor Terms and ShipVia defaults where available. Company-specific custom data masks from Exxas migrate to Epicor UD fields on the Customer table. Linked contacts in Exxas attach to the Customer record via ContactFunc records in Epicor.

Exxas Sales pipeline stages map to Epicor OrderHed stages (Open, Pending, Closed). Open Exxas Deals migrate as Epicor Sales Orders in Open status; closed Deals migrate as historical Orders. Deal amounts in CHF or EUR migrate to Epicor TotalOrder value in the customer's currency. Custom deal fields become UD fields on OrderHed.

Exxas pipeline stage names are extracted as a distinct list and configured as Epicor OrderHed Status values. Each Epicor Status gets a Probability percentage matching the Exxas stage probability if configured. Stage ordering is preserved in Epicor's Status Code sequence.

Exxas Service module tickets map to Epicor Service Call records. Ticket status (Offen/In Bearbeitung/Geschlossen) translates to Epicor Open/In Process/Closed. Assigned technician from Exxas maps to Epicor EmployeeNum via owner email resolution. Ticket priority and linked customer asset migrate as Service Call detail lines and RelatedCustProd records.

Exxas Projects with their task hierarchies and Kanban boards map to Epicor Project and ProjectTask records. Sprint assignments in Exxas become Epicor Project Phase records with start and end dates. Employee resource assignments on Exxas tasks link to Epicor ResourceGrp or Labor records via employee email-to-EmployeeNum lookup. Sprint burndown metrics are noted as non-transferable; Epicor recalculates these on first project refresh.

Exxas Products map to Epicor Part records with TypeCode of Item or Service. Exxas pricing tiers migrate as Epicor PartPlant PriceList entries. Stock-on-hand from Exxas moves to Epicor PartWhse OnHandQty by warehouse. BOM relationships from Exxas migrate as Epicor BOM and BOMAsm records. Warehouse-specific bin locations in Exxas flag a manual reconciliation step post-migration because Epicor bin assignment requires site-specific configuration.

Exxas Employee records with job title, department, start date, and effective-dated compensation map to Epicor Employee. Historical pay rates and compensation effective-date ranges migrate as Epicor EmpBasicPay records. Swiss-specific benefit fields that cannot map to Epicor UD fields are flagged for manual HR admin review post-migration.

Exxas payroll runs are tightly coupled to Swiss social security and tax calculation engines and do not transfer as live payroll records into Epicor. We export employee compensation rates and employment history as a CSV report for the customer's HR admin to reference when setting up Epicor Payroll. Epicor's Swiss payroll module or third-party integration handles live payroll going forward.

Exxas Finance chart of accounts maps to Epicor GL Account. Account code structure and description migrate as-is. Account type (Asset, Liability, Equity, Revenue, Expense) maps to Epicor Category. Swiss CHF functional currency in Exxas maps to Epicor's base currency setup on initial tenant configuration.

Exxas open Accounts Payable and Accounts Receivable records migrate as Epicor APInvoiceHed and ARInvoiceHed respectively. Open invoice amounts, due dates, and vendor/customer references transfer. Historical closed periods from Exxas migrate as read-only GL Journal entries in Epicor; they are not posted to open AP/AR but are preserved in the GL for audit continuity.

Exxas Finance journal entries migrate to Epicor GL Journal with debit and credit line detail. Each journal line's account reference resolves to the Epicor GL Account created from the chart of accounts mapping. Journal date and description preserve. Closed period journal entries from Exxas migrate as posted GL Journal records in Epicor with locked Editable flag set to false.

Exxas Marketing campaigns with lead flows map to Epicor Marketing Campaign records. Campaign status and target audience migrate. Exxas leads generated in the Marketing module and passed to Sales migrate as Epicor Prospect or Lead records depending on qualification status. Marketing campaign engagement metrics are noted as non-transferable as they are calculated by Exxas' own marketing attribution engine.

Exxas custom data masks with individual fields per entity category map to Epicor UD fields on the corresponding table (Customer, OrderHed, Part, Project, Employee, etc.). We extract all custom field definitions and their data types during scoping, then provision equivalent UD fields in Epicor before data load begins. Complex Exxas data mask logic (conditional visibility, cross-field dependencies) cannot transfer and is documented for manual rebuild in Epicor Kinetic.

Exxas Personal Customer Portal-facing records — invoices, orders, support tickets, and asset records available to customers — migrate as data attached to the relevant Epicor Customer record. Portal configuration (branding, layout, permissions) does not migrate; Epicor Experience or a separate portal implementation handles this as a post-migration project.