Migrate from e-Emphasys ERP to Infor CloudSuite Corporate

e-Emphasys Customer records combine contact details, billing addresses, OEM affiliations, and branch assignments in one record. Infor CloudSuite separates these into Business Partner (the party entity) with separate Address, Contact, and Business Partner Role records. We extract e-Emphasys customer fields, split address and contact data into Infor CloudSuite address book structures, and preserve branch-level assignments as Business Partner Assignment records. OEM affiliation codes from e-Emphasys map to Infor Business Partner Classification codes that we configure during schema setup.

e-Emphasys serialized equipment records carry OEM codes, VIN-equivalent identifiers, branch assignment, current status (new/used/rental/demo), and OEM warranty associations. These map to Infor CloudSuite Item Master records with serial number tracking, item classification as equipment, and status codes mapped to Infor Item Availability codes. The e-Emphasys OEM equipment code becomes the Infor Item Cross Reference with a primary supplier assignment. Branch assignment maps to Infor Warehouse or Site assignment on the Item Master.

e-Emphasys tracks both serialized and non-serialized parts with bin locations, vendor links, cost/price tiers, stock levels, and reorder points. These map to Infor CloudSuite Item Master records with appropriate stocking type (traced for serialized, bulk for non-serialized). Bin locations map to Infor Warehouse Location codes. Vendor links map to Business Partner (Supplier role) assignments on the Item Master. Cost and price tiers migrate as commercial trade agreements in Infor CloudSuite's pricing structure.

e-Emphasys work orders tie to equipment records, technicians, line items for parts used, labor hours, and warranty claim associations. These map to Infor CloudSuite Service Management work orders with the source equipment linked via Item Master serial number reference. Labor hours and rates map to Infor Service Order operations with the technician assigned as a resource. Warranty claim associations migrate as Service Order cause and responsibility references. We flag any work order custom fields that require manual field creation in Infor OS before migration.

e-Emphasys rental contracts store equipment assignments, daily/weekly/monthly billing tier structures, equipment swap records, and early return conditions in a single contract entity. Infor CloudSuite separates these into a Rent Contract header, separate rate schedule lines, and equipment assignment records. We extract all rate tiers into an intermediate schema during discovery, map the dominant billing structure to Infor Rent Management contract configuration, and flag any multi-tier rate schedules or swap conditions that exceed Infor's native contract structure. Active contracts require manual reconciliation before go-live.

e-Emphasys whole goods sales orders and quotes link customer and equipment records with pricing tiers, OEM incentives, and order status. These map to Infor CloudSuite Order Management sales orders with customer reference to Business Partner, equipment reference to Item Master, and pricing via Infor pricing structures. Order status from e-Emphasys maps to Infor Order Status codes. Open orders in progress at migration time require special handling with a delta migration step during cutover.

e-Emphasys GL accounts, chart of accounts structure, journal entries, and period balances export from the financial module. These map to Infor CloudSuite Financials GL Account Master and Journal Entry records. We preserve the account code structure and period associations, and map account types to Infor Financials account categories. Historical period balances migrate as opening balances in Infor Financials; we recommend the customer coordinates with their Infor implementation partner on year-end close entries before migration.

e-Emphasys vendor invoices, payment records, and PO-to-invoice associations migrate to Infor CloudSuite Financials AP module with vendor records mapped to Business Partner (Supplier role). We preserve invoice-to-PO associations where they exist in e-Emphasys, and map payment history to Infor AP Payment records. Open AP balances at migration date migrate as outstanding invoices requiring payment in Infor.

e-Emphasys customer invoices, payments, and AR aging data export with full customer linkage. These map to Infor CloudSuite Financials AR module with customer references mapped to Business Partner (Customer role). Open invoice balances and payment history preserve with customer linkage. We generate an AR aging report from e-Emphasys as of the migration date and enter opening AR balances in Infor Financials accordingly.

e-Emphasys employee records include labor rates, certifications, branch assignments, and department affiliations. These map to Infor CloudSuite Employee records with labor category and rate schedule mapped to Infor's payroll or service resource configuration. Certifications tied to OEM specializations (Caterpillar, John Deere) map to Infor Employee Skill records. Custom labor rate schedules in e-Emphasys that exceed Infor's standard rate configuration are flagged for manual verification with the customer's Infor administrator before migration.

e-Emphasys warranty records tie to serialized equipment and OEM claims with claim history, coverage periods, and claim status. These map to Infor CloudSuite Service Management warranty entitlement records linked to the equipment Item Master serial number. OEM codes from e-Emphasys map to Infor Warranty Plan definitions that we configure during schema setup. Active open warranty claims require reconciliation against the destination warranty plan coverage limits before go-live.

e-Emphasys supports user-defined fields across many modules. We identify all active custom fields during discovery by inspecting the source database schema, documenting their data types and values. These map to Infor OS Custom Properties on the equivalent Infor CloudSuite objects. Some e-Emphasys custom fields may have no natural Infor CloudSuite equivalent; we document these as manual-entry fields in a supplementary spreadsheet for the customer's admin to recreate post-migration. Custom fields on e-Emphasys reports also require rebuild as Infor OS reports or Birst dashboards.