Migrate from Edara to Infor CloudSuite Corporate

Edara's chart of accounts with account codes, names, types, and active/inactive status maps 1:1 into Infor CloudSuite's COA structure. Account types (Asset, Liability, Equity, Revenue, Expense) map to Infor account categories, and the account code format is preserved as-is. We use Infor's Import Source Tables form to define the Edara SQL source table mapping and load accounts before any transactional data to satisfy foreign-key dependencies in Infor's COA table.

Edara customer records with billing address, shipping address, contact information, payment terms, and customer currency assignment map to Infor CloudSuite Business Partner records with BP Type = Customer. The BP Address Book functionality in Infor handles multiple ship-to addresses per customer, which Edara models as separate customer records in some configurations; we detect duplicate BP numbers during scoping and merge into a single BP with multiple addresses where applicable.

Edara vendor master records including addresses, tax IDs, and default payment terms map to Infor CloudSuite Business Partner records with BP Type = Supplier. We preserve the vendor's default currency and reconcile the open PO balance from Edara's purchase order aging report against the vendor record in Infor before committing. Duplicate vendor names are flagged for manual resolution during reconciliation.

Edara item master records with SKU, description, cost, price, unit-of-measure conversions, and warehouse assignments map to Infor CloudSuite Item records. The inventory valuation method (FIFO, Weighted Average, Standard) per item is preserved as a configuration field on the Infor item record. If Edara uses lot tracking or serial number management, we map those to Infor's lot and serial number fields which are configured per item.

Edara sales orders with header data (order number, date, customer reference, salesperson, terms) and line items (item, quantity, price, discount, tax) map to Infor CloudSuite Sales Orders. The mapping handles Pro-plan extraction staging for customers with over 30,000 orders in a billing cycle by chunking the export in monthly batches aligned to the billing period. Open orders and closed orders both migrate; closed order status is preserved in a custom Infor field for audit. Orders are loaded after Business Partners to satisfy the customer BP lookup.

Edara purchase orders with vendor assignments, line items, PO approval status, and linked receipt records map to Infor CloudSuite Purchase Orders. PO approval status from Edara becomes a user-defined field in Infor; we do not replicate Edara's internal approval workflow state because Infor PO approvals are rebuilt as part of the destination configuration. Any linked receipt records are migrated as separate inbound receipt transactions in Infor's receiving module.

Open receivables and payables require reconciliation of outstanding amounts, due dates, and currency against Edara's aging reports. We export the aging detail, map each open document to its Infor equivalent (AR Invoice, AP Invoice), and flag discrepancies between the aging total and the general ledger trial balance for the customer's accountant to resolve before we commit the open document ledger. Multi-currency open documents carry both the original transaction currency and the Infor functional currency with exchange rate reference.

Edara warehouse records, stock levels, and bin locations map to Infor CloudSuite warehouse and inventory records. Multi-warehouse setups in Edara map to multiple Infor warehouse codes. We flag negative stock entries detected in Edara for customer review before loading; Infor's inventory validation rules may reject negative quantities on standard item types. If Edara uses cross-warehouse transfers, we map those to Infor's internal transfer order model.

Fixed asset records are only fully accessible on Edara Ultimate plan, which limits the acquisition cost, accumulated depreciation, depreciation method, and asset useful life export for Pro and Basic customers. We extract what is accessible through financial reports and reconcile against the trial balance. Any gap between the asset register and the general ledger is flagged for the customer's accountant to manually re-enter or adjust before committing to Infor's Fixed Assets module. Full depreciation schedule continuity is not guaranteed for non-Ultimate Edara customers.

Edara POS register definitions including base register fee, additional register assignments, and salesperson attribution per register are exported as configuration records. These do not map directly to a standard Infor CloudSuite POS object because POS capability varies by CloudSuite edition. We deliver a written register inventory with the full register count, assigned salespersons, and per-location breakdown so the customer's Infor implementation team can configure POS appropriately for their edition.

Edara multi-currency support (available on Pro and above) includes exchange rate history alongside transactional data. We export the rate history and configure Infor CloudSuite's exchange rate table with the same effective dates and rates. Multi-currency open AR/AP documents are migrated with the original transaction currency reference preserved so that realized and unrealized FX gains/losses can be recalculated in Infor's currency revaluation process post-migration.

Edara salesperson records used in sales orders and POS transactions map to Infor CloudSuite Salesperson records. Salesperson attribution on historical orders is preserved by mapping the Edara salesperson ID to the Infor salesperson code during order import. If Edara's per-salesperson add-on pricing was active, we capture the full salesperson roster count to include in the cost-of-change comparison versus Infor's pricing model.