Migrate your Ostendo data

Customer records are held in the CUSTOMER MASTER table and are standard master data. We export via CSV or Excel through the Data Exporting function, preserving all displayed fields and contact details. No known schema variation between versions.

ITEMMASTER holds all items, including Primary Supplier linkage. Standard fields include item code, description, unit cost, and stock levels. We extract the full item record including supplier associations and custom list fields set by the user.

Purchase Orders are standard transactional records in Ostendo. We export line items, quantities, supplier linkage, and order status. Header-level and line-level fields are both captured from the transactional tables.

Sales Orders cover different Order Styles for various sales activities. We extract the full order hierarchy including line items, pricing, and status. Ostendo's POS function also generates orders which are included in the same table structure.

Work Orders and manufacturing orders are tracked through the Assignment Board and order scripts. We export job details, routing, and status. Multi-level BOMs may require flattening during transformation to match the destination schema.

Timesheets are linked to Work Orders and Jobs. The mobile field capture layer (Freeway Mobile) writes time entries including GPS and materials issued. We extract all time entries but flag records with non-standard custom capture fields for manual field mapping review.

Stock levels and multi-site inventory are tracked with serial number tracking per location. We export stock quantities, locations, bin references, and serial numbers. Multi-site records are normalised to the destination's warehouse or location object.

Service Zones group assets geographically for field service deployment. Stock Locations define physical or logical inventory positions. Both are standard reference tables and migrate cleanly as address or zone entities.

Asset records are linked to Service Zones and can carry meter readings and equipment checks. We export asset master data including maintenance history and current status.

User records are managed through User Security and Options. Ostendo uses concurrent user licensing (not named users), which is a significant difference from most modern SaaS platforms. We export user identity and role records but note that destination systems may price differently per user.

Ostendo supports user-defined templates in the mobile capture layer and custom list fields per screen. Custom fields are stored per-object. We flag all custom field definitions during discovery and map them to destination custom fields, noting any that have no direct equivalent.

Ostendo's SQL-based Report Writer creates saved reports, inquiries, and pivot tables that reference Ostendo-specific table structures. These reports have no direct equivalent in target ERP or CRM systems and are excluded from migration. We export the report definitions as documentation only.