Migrate from AltheaSuite to Infor CloudSuite Corporate

AltheaSuite Items map to Infor CloudSuite Product records. Standard fields (item code, name, description, unit of measure, cost, price) migrate directly. Custom Item fields (text, number, fractional, lookup value, date time types confirmed in AltheaSuite documentation) map to Infor extended data structure fields with explicit type conversion. Reorder levels and reorder quantities become Infor planning parameters. We request a full enumeration of all custom Item fields from the customer during discovery because AltheaSuite does not expose custom field definitions via public API.

AltheaSuite serial-to-item assignments are extracted as a child table mapping each serial number to its parent Item. Infor CloudSuite Industrial manages serial numbers as inline item attributes or as separate Lot/Serial records depending on the site's configuration. We re-associate each serial record at the destination, flagging any orphaned serial numbers (no parent Item) for manual resolution before finalizing the import. FEFO logic at the destination uses expiry dates carried from AltheaSuite lot records.

AltheaSuite lot-controlled items carry lot number and expiry date metadata as separate assignment records. We migrate the full lot-to-item mapping with expiry dates intact. Infor CloudSuite Industrial's FEFO (First Expired First Out) logic uses expiry date fields for inventory allocation. Any lot record without an expiry date is assigned a null expiry and flagged for the customer's review.

AltheaSuite nested BOM structures with sub-assemblies are flattened during migration mapping. Each level of the BOM hierarchy is extracted with its parent component and quantity-per, then reconstructed in Infor CloudSuite Industrial's BOM master as parent-item to component-item relationships with the correct quantity-per and operation sequence. Routing definitions (work centers, operation sequences, cycle times) require explicit value mapping if AltheaSuite stores operation-level data separately from the BOM header.

AltheaSuite Work Orders map to Infor CloudSuite Industrial Work Orders with header data (work order number, status, priority, planned start and completion dates) and the linked multi-level BOM reference. Step-level labor and machine time entries migrate as a child table if the destination configuration supports time entries on Work Order operations. Work Order status (open, released, in progress, complete, closed) maps to Infor's status codes with explicit value translation during import.

AltheaSuite Customer records migrate to Infor CloudSuite Business Partner records with customer role. Contact details (name, phone, email), billing and shipping addresses, and account-level fields transfer intact. Infor requires a Business Partner to be designated as Customer role before it can be referenced on Sales Orders. We ensure Customer role designation is applied during the Business Partner import phase.

AltheaSuite Vendor records migrate to Infor CloudSuite Business Partner records with supplier role. Contact details, addresses, and supplier-level fields transfer intact. Vendor-managed inventory flags from AltheaSuite map to a boolean property on the Supplier record in Infor. Supplier role designation is applied during the Business Partner import phase before any Purchase Order import references it.

AltheaSuite Sales Orders migrate to Infor CloudSuite Sales Orders with header data (order number, customer reference, order date, terms) and line items (item, quantity, unit price, discount). Order-to-delivery linkage is preserved where AltheaSuite tracks delivery assignments. Fulfillment status (open, partial, complete) maps to Infor's order status codes with explicit value translation. Multi-currency and landed-cost fields require explicit value mapping against Infor's currency configuration.

AltheaSuite Purchase Orders migrate to Infor CloudSuite Purchase Orders with header and line item data. Line items (item, quantity, cost, discount) transfer directly. Multi-currency and landed-cost fields require explicit value mapping against Infor's purchase order schema. We validate vendor references against the Business Partner import before Purchase Order records are loaded.

AltheaSuite integrated POS transactions are point-of-sale records tied to specific store sessions and payment events. Infor CloudSuite Industrial does not include a POS module by default; distribution and retail scenarios use Infor CloudSuite Distribution or a separate POS integration. We flag POS transaction history for the customer's decision: archive in a separate database for audit compliance, or exclude from migration scope as not applicable to the destination ERP.