Migrate from Ostendo to Microsoft Dynamics 365 Business Central

Ostendo CUSTOMER MASTER records map to Dynamics 365 Customer (Account) entities. We preserve customer code, name, contact details, addresses, payment terms, and tax registration numbers. The CUSTOMERMASTER customer type flag (Customer, Supplier, or Both) determines whether we create a Customer record only, or a Customer and Vendor pair in Dynamics 365. Dedup key is customer code. Tax ID and ABN/ACN migrate to the Tax Identification Number fields.

Ostendo ITEMMASTER maps to Dynamics 365 Released Product with the product type (Item, Service, or BOM) preserved from the item's Ostendo category. Primary Supplier linkage from ITEMMASTER becomes the default vendor on the product's Vendor catalog. Unit cost, unit of measure, and stock level fields migrate to the appropriate inventory dimensions. For items with serial number tracking, we enable Serial number control in Dynamics 365 before stock import.

Ostendo Purchase Orders map to Dynamics 365 Purchase Orders. Header fields (vendor, order date, delivery address, terms) and line fields (item number, quantity, unit cost, line amount) migrate directly. PO status from Ostendo (Open, Received, Closed, Cancelled) maps to the corresponding Dynamics 365 receipt status. Received lines with partial receipt status require careful delta handling to avoid duplicate receipt entries.

Ostendo Sales Orders map to Microsoft Dynamics 365 Sales Orders. We preserve the Order Style distinction (standard sale, return, service order) through the Microsoft Dynamics 365 Sales Order type field. Line items, pricing, discounts, and tax migrate to the corresponding Dynamics 365 structure. OSTENDO's POS function-generated orders are identified by their source flag and migrated as Sales Orders with a POS reference field. Customer item numbers from Ostendo lines are preserved in the Customer Line Reference field.

Ostendo Work Orders map to Dynamics 365 Production Orders. Job details, routing, BOM version, scheduled start and end dates, and status migrate. Multi-level BOMs in Ostendo may require flattening during transformation: we expand each BOM to its lowest-level components and create Dynamics 365 Production Order lines matching the bill of materials structure. The Ostendo Assignment Board scheduling data maps to Production Order scheduling in FinOps. Site and warehouse assignment from the Work Order transfers to the Production Order warehouse and site fields.

Ostendo stock quantities per location map to Dynamics 365 On-hand entries using the inventory dimension combination of Site, Warehouse, and Location. Serial number tracking per location in Ostendo maps to Dynamics 365 serial number inventory dimensions on a one-to-one basis. Multi-site records from Ostendo Service Zones and Stock Locations create separate Site and Warehouse records in Dynamics 365 before on-hand quantities are imported. We validate that all destination sites and warehouses exist before writing inventory.

Ostendo Asset records linked to Service Zones map to Dynamics 365 Fixed Assets. Asset master data including asset number, name, acquisition date, acquisition cost, depreciation method, and current book value migrate. Maintenance history, meter readings, and equipment check records from the asset form migrate as Fixed Asset supplementary records. The link between Fixed Asset and the responsible Site (from the Ostendo Service Zone) is preserved through a custom field on the Fixed Asset record.

Ostendo Stock Locations map to a hierarchy of Site (top-level operational unit), Warehouse (storage location), and Location (bin or shelf within warehouse) in Dynamics 365. Service Zones map to Site records because they represent geographic groupings for field service deployment. We preserve the zone-to-location linkage so that Dynamics 365 Field Service can inherit the geographic service area assignment from the migrated Service Zone.

Ostendo timesheets linked to Work Orders and Jobs map to Dynamics 365 Time Entry records. The mobile Freeway Mobile capture layer writes time entries including GPS and materials issued; we extract these as standard time entries and preserve the GPS coordinates in a custom field for audit. Time entries linked to Production Orders become Project Time Entries if the destination uses Project Management; otherwise they migrate as time registration against the Worker. The linking of time entries to the originating Work Order number is preserved in the Description or External Reference field.

Ostendo User records from User Security and Options map to Dynamics 365 Worker records (for FinOps HR or Project modules) or System User records (for Business Central). Ostendo's concurrent-user licensing means the customer typically has more named users than concurrent seats; we capture the full user record count during discovery and map all users to named-user equivalents, alerting the customer to any licensing delta. Active users become active Workers; inactive users become inactive Workers with a flag requiring admin review.

Ostendo Freeway Mobile user-defined templates with checklists, compliance forms, and QA inspection fields map to custom fields on the Worker, Asset, or Work Order entities in Dynamics 365 Field Service. These require manual field definition in the destination because they have no standard export format. We flag all custom template definitions during discovery, document each as a written field spec for the customer's admin to recreate in the Field Service customizer, and provide a mapping sheet linking the original Freeway Mobile template name to the newly created Dynamics 365 custom field names.

Ostendo's SQL-based Report Writer and saved queries reference Ostendo-specific table names and schemas that have no direct equivalent in Dynamics 365. We do not migrate reports. We deliver a written inventory of every saved report and query in the Ostendo environment, documenting the source tables, filters, and output format, so the customer's Dynamics 365 admin or implementation partner can rebuild equivalent reports in Power BI or the Dynamics 365 report designer.