Migrate from eBIZ SMARTZ Business ERP to Infor CloudSuite Corporate

eBIZ SMARTZ Customer master records map to Infor Customer or Party depending on the destination CloudSuite product line. The 360-degree customer view (consolidated order history, invoice records, and payment status) transfers as related transactional records linked to the Customer. We preserve the customer account number and tax registration as distinct fields for reconciliation against Infor's party-level schema. Dedupe matching uses customer account number as the anchor key.

eBIZ SMARTZ Orders map to Infor Sales Order or Customer Order depending on the destination CloudSuite product line. The transactional linkage to the Customer record is preserved through the party lookup. Order status, order dates, and line items transfer with field-type mapping (date formats, numeric precision) applied during the transformation step. We flag any orders that reference inventory items not present in the destination item master for customer resolution before production load.

eBIZ SMARTZ Invoice records map to Infor Invoice records with references preserved to the originating Customer and Order. Payment reconciliation status from the consolidated database transfers to Infor's open invoice tracking. We handle the mapping from eBIZ SMARTZ invoice numbering conventions to Infor's document number structure during the transform phase.

eBIZ SMARTZ Payment records map to Infor Payment or Cash Receipt records linked to the associated Customer and Invoice for cash application. Payment method codes (cash, cheque, bank transfer, card) map to Infor payment type codes. Payment dates and amounts transfer with currency handling applied for multi-currency scenarios.

The eBIZ SMARTZ chart of accounts (multi-level structure) maps to Infor's account master with attention to account type, cost-center assignment, and currency posting rules. We analyze the eBIZ SMARTZ account hierarchy and flatten it into Infor's account structure, preserving account codes and descriptions. Custom accounts added during eBIZ SMARTZ implementation are flagged for the customer's Infor administrator to validate against industry-specific account templates.

Historical journal entries and subledger transactions require sequencing to preserve the audit trail through the cutover window. We extract journal entries with full line-item detail (account, debit, credit, cost center, description, source module) and sequence them chronologically. Infor CloudSuite's migration utility supports stored procedures for table mapping; we use these or custom stored procedures for journal entry imports that require multi-line validation before commit.

eBIZ SMARTZ corporate headquarters and division or operating location structures map to Infor organizational hierarchy entities. A single eBIZ SMARTZ operating location may represent a company, an operating unit, or a site depending on the customer's organizational structure. We split the source hierarchy into the appropriate Infor entities (Company code, Operating Unit, Site) during the transform phase based on the customer's intended Infor deployment model.

eBIZ SMARTZ employee records (from the HR module) map to Infor Worker or Employee records depending on the destination CloudSuite product line. We transfer employee number, name, department, cost center, employment status, and compensation history where the destination schema supports historical compensation fields. HR benefits data requires field-level mapping to Infor's HR schema and may require the customer's Infor HR administrator to validate benefit plan mappings.

eBIZ SMARTZ item or product master records map to Infor Item or Product depending on the destination CloudSuite product line. Item codes, descriptions, unit of measure, and costing method transfer with field-type mapping applied. Inventory valuation method from eBIZ SMARTZ maps to Infor's costing configuration. Items flagged as active or inactive transfer with the status preserved.

eBIZ SMARTZ asset records and procurement transactions (purchase orders, receipts) map to Infor Fixed Asset and Procurement records. Asset acquisition cost, depreciation method, and asset life transfer to Infor's fixed asset master. Open purchase orders map to Infor Purchase Order records with line items and vendor references. We flag assets with non-standard depreciation schedules for customer review before Infor configuration.

eBIZ SMARTZ multi-level cost center structures map to Infor cost objects. The cost center hierarchy (category levels, parent assignments) transfers and is validated against Infor's cost center structure. Project-linked cost centers require additional mapping to Infor project cost objects if the destination CloudSuite product includes project accounting.