Migrate your Comarch Field Service Management data

Work Orders are the primary object in Comarch FSM. Each Work Order contains customer reference, asset link, parts used, time entries, checklist data, and status history. We migrate Work Orders with full field-level fidelity including nested line items and attachments. Completed and in-progress records are handled identically.

Technicians represent field workers with assigned skills, certifications, work zones, and schedule availability. We preserve the skill-to-certification mapping and territory assignments during migration. Active and inactive technician records are migrated as-is; status can be toggled post-import.

Customer records may link to external CRM systems via the Integration Hub. Where Comarch holds a thin Customer object and the destination system maintains the authoritative record, we map by customer ID and flag references that need manual re-linkage. Address and contact fields are migrated directly.

Assets are equipment records linked to Customer locations with maintenance history, installed parts, and upcoming service schedules. Asset-to-location relationships require field mapping because naming conventions vary between source and destination systems. We preserve the full parts tree per asset.

Parts catalogs include SKU, description, unit cost, and current stock levels. We migrate part definitions and current inventory quantities but flag that stock levels may need to be zeroed at cutover to avoid inconsistent post-migration reporting. Reorder thresholds and supplier links are carried forward as custom fields.

Schedule records capture technician availability windows, break blocks, and travel time. Since schedules are date-sensitive, we migrate future-dated schedule blocks and leave historical schedule records as optional scope items. Recurring schedule patterns are extracted and reconstructed at the destination.

Dispatch records link a Work Order to a Technician with an assigned time window and priority level. We preserve the dispatcher assignment history and priority flags. Where the destination uses a different dispatch model, we map to the nearest equivalent and flag for review.

Comarch supports user-defined fields per module. Custom properties are migrated as supplementary fields attached to their parent object. We require schema inspection of the source tenant before migration to enumerate custom field names and data types for accurate field mapping.

Work Orders and Assets can carry file attachments including photos, PDFs, and signed documents. We extract binary files and attach them to the corresponding record at the destination using file-type preservation. Large attachment volumes may affect transfer time estimates.

Comarch's reporting layer is derived from transactional data and does not store a separate report-definition export. We do not migrate pre-built reports; we recommend rebuilding custom reports at the destination using the migrated transactional data as source. Standard report templates are documented for manual reconstruction.

SLA definitions attach to Work Order types and define response and resolution windows. We extract SLA rules and map them to the destination's SLA framework, flagging cases where target metrics differ (e.g., 4-hour vs. next-business-day response).