Migrate from Ostendo to Infor CloudSuite Corporate

Ostendo CUSTOMER MASTER records map to Infor Cloudsuite Customer or Party records depending on the CloudSuite product line (CSI uses Customer; M3 uses Business Partner). All displayed fields including contact details, billing address, and payment terms export from Ostendo via CSV and load through the Import Source Tables form in the Infor Migration Utility. We preserve the Ostendo customer code as the external reference identifier for audit trails.

Ostendo ITEMMASTER maps to Infor Cloudsuite Item records with Primary Supplier linkage preserved. Standard fields (item code, description, unit cost, stock levels) migrate directly. We extract supplier association records and load them to the Item Supplier table in Infor. Where Ostendo holds product images as attachments, we map those to Infor Document Management or the item record's image field depending on the CloudSuite edition.

Ostendo Purchase Orders with line items, quantities, supplier linkage, and order status map to Infor Cloudsuite Purchase Orders. We export both header and line-level fields from Ostendo's Data Exporting function and load through the Migration Utility, preserving order status, expected delivery dates, and any landed-cost fields. Open purchase orders migrate as open; closed and received orders migrate with full receipt history.

Ostendo Sales Orders covering different Order Styles map to Infor Cloudsuite Sales Orders with line items, pricing, and status. We extract the full order hierarchy including discount rows and tax calculations. POS-generated orders from Ostendo's POS function map to Infor POS transactions. The Infor Migration Utility requires open orders to be completed and posted in the source system before migration begins; we coordinate the freeze window with the customer to capture any in-flight orders.

Ostendo Work Orders and manufacturing orders map to Infor Cloudsuite Production Orders. Multi-level Bills of Materials (BOMs) from Ostendo's routing and assembly layers require flattening during transformation because Infor's Migration Utility expects a flat BOM structure. We extract the full BOM hierarchy, resolve each component to an Item record in Infor, and write the flattened BOM to the Infor production order. Routing steps map to Infor operation sequences.

Ostendo timesheets linked to Work Orders and Jobs, including Freeway Mobile entries with GPS and materials issued, map to Infor Cloudsuite Time and Labor records. We extract all time entries and load them to the appropriate Work Order or Production Order in Infor. Entries with GPS coordinates map to Infor's mobile time capture location fields if the target CloudSuite edition includes the Service Management module.

Ostendo stock levels, serial number tracking, and multi-site quantities map to Infor Cloudsuite Inventory On Hand records. We export stock quantities, bin references, and serial numbers per location, normalising multi-site records into Infor's site-based inventory structure. Serial number tracking migrates as inventory serial number records linked to the Item.

Ostendo Service Zones and Stock Locations map to Infor Cloudsuite Location or Warehouse records. Both are standard reference tables in Ostendo and migrate cleanly as address and bin-structure records. We preserve the zone-to-location mapping for field service routing if Infor Service Management is in scope.

Ostendo Asset records linked to Service Zones, with meter readings and equipment checks, map to Infor Cloudsuite Asset records. We export asset master data including maintenance history and current status. Preventive maintenance schedules require manual recreation in Infor Asset Management as the scheduling engine is destination-specific.

Ostendo user records managed through User Security and Options export as named-user records for Infor Cloudsuite. Ostendo's concurrent-user licensing (where most businesses use 25-40% of headcount as simultaneous seats) does not translate directly to Infor's named-user model. We extract the full user roster and map each to a named Infor User, flagging any user whose activity level would exceed the intended named-user licence count for the customer's review before provisioning.

Ostendo Freeway Mobile user-defined templates for field data capture (checklists, compliance forms, QA inspections) store custom fields per object without a standard export format. We flag all custom template fields during discovery, map each to an Infor OS custom field on the equivalent object, and alert the customer to any destination fields that cannot hold equivalent data without manual recreation. This is a manual mapping exercise requiring the customer's functional leads to confirm data equivalence.