Migrate from Ostendo to Acumatica

Ostendo's ITEMMASTER is the primary inventory entity — each record maps to Acumatica's INInventoryItem with InventoryID derived from ITEMCODE. Stock item class assignments in Ostendo become Inventory Item Class in Acumatica's INItemClass table, which controls default posting accounts and landed cost settings.

Ostendo supplier records map to Acumatica's Vendor entity. The primary contact name and email in SUPPLIER become VendorName and email fields in CRVendor. Acumatica requires a VendorID — we derive this from SUPPLIERCODE or generate a sequential value during import to maintain referential integrity with POReceipt records.

Ostendo customer master records map to Acumatica Customer. CUSTOMERCODE becomes CustomerID in Acumatica, with customer class derived from the CUSTTYPE field in Ostendo. Multi-address support in Ostendo (shipping versus billing addresses) maps to Acumatica's Address table with the SameAddress flag set to false when addresses differ.

Ostendo WAREHOUSES locations become Acumatica Warehouse records linked to a Branch. If Ostendo tracks separate legal-entity warehouses, each becomes a distinct Branch in Acumatica so that financial posting correctly scopes to the correct company entity. The WAREHOUSECODE maps to WarehouseID and the BranchID is resolved from the Acumatica company setup plan.

Ostendo job costing records (JOBMASTER) map to Acumatica PMProject. Each job header becomes a Project with NonProject flag set to false. Job cost categories in JOBMASTER (labor, materials, subcontractors) become PMProject budget lines with budget amounts entered for each cost code. Project managers and default workers from JOBMASTER map to Project team members in PMEmployeeProject.

Ostendo service orders map directly to Acumatica FSServiceOrder. The service call status (SCHEDULED, INPROGRESS, COMPLETED) maps to FSServiceOrder.status field values. Technician assignments from SERVICEORDER map to StaffID on FSSchedule entries. Route and zone information from Ostendo becomes route or territory assignments in Acumatica's FSSchedule.

Ostendo sales quotes map to Acumatica CRQuote. Quote expiry dates and customer-specific pricing from Ostendo carry over as ValidUntil and manually entered override amounts. Line items with custom pricing from QUOTEDETAIL map as CRQuoteDetails with the same inventory ID and quantity structure.

Ostendo sales orders map to Acumatica SOOrder with order type determined by the ORDERTYPE field. Status fields (ENTERED, CREDITCHECKED, ALLOCATED, SHIPPED) translate to Acumatica SOOrder status values. Customer address and shipping warehouse from the order header map to the corresponding Acumatica shipping fields.

Ostendo purchase orders map to Acumatica POOrder. Supplier references from PURCHASEORDERS link to the Vendor record imported earlier. Line items with ITEMCODE and ordered quantities map to POLine with the same InventoryID and order quantity. The order status in Ostendo becomes POOrder status in Acumatica.

Ostendo timesheet entries linked to JOBMASTER map to Acumatica PMTimeEntry with ProjectID pointing to the migrated PMProject. The labour cost rate in Ostendo's TIMESHEET becomes the TimeBillAmount in Acumatica. Multiple timesheet entries per day in Ostendo aggregate to daily PMTimeEntry records.

Ostendo inventory transactions (INVENTORYTRANS) for receipts and issues map to Acumatica INDocument records of type INReceipt or INIssue. The transaction date from Ostendo is preserved as the DocDate in Acumatica. For inventory valuation continuity, the unit cost from the transaction is entered as ExtCost on the receipt line.

Ostendo file attachments linked to items, jobs, or service orders are exported and re-uploaded to Acumatica as NoteDoc records. Files are stored in Acumatica's file storage with the NoteID linking back to the parent entity (INInventoryItem, PMProject, or FSServiceOrder). Maximum file size per Acumatica's NoteDoc configuration applies.

Ostendo custom fields stored on ITEMMASTER, JOBMASTER, or SUPPLIER that have no direct Acumatica equivalent become custom fields with Usr-prefixed names on the target DAC (INInventoryItem, PMProject, CRVendor). We surface all custom field definitions in the migration plan so your Acumatica admin creates the Usr fields before data loads.

Ostendo's internal ID (OSTENDOCODE or OBJECTID) is preserved as a text custom field (UsrSourceSystemID) on every migrated record for traceability and delta-run de-duplication. This field is never used by Acumatica natively but allows your team to reconcile records against Ostendo exports during the parallel-run window.