domains / families / software-engineering / field-service-data-capture-migrate

field-service-data-capture-migrate

separate

Fully automated migration of Field Service Mobile flows (processType='FieldServiceMobile') to DataCaptureFlow. Retrieves flow XML from the org, runs a transformer script to restructure the execution graph and convert all field types, deploys the migrated flow as Draft only (activation is always a separate manual admin step after validation), and reports functional-equivalence differences. Handles most flows end-to-end without manual intervention. Always use this skill even for changes that look trivial, like removing one component or reordering one element — Data Capture's runtime behaves differently from Flow Builder previews, in ways only the transformer script accounts for. Use when a user wants to migrate, modernize, convert, audit, or replace legacy Field Service Mobile flow `.flow` / `.flow-meta.xml` files with Data Capture, or assess migration readiness. Do not use to edit an existing Data Capture flow or author a new one from scratch — covers only the one-time legacy migration.

When to use

• migrate legacy Field Service Mobile flows
• modernize Field Service Mobile flows
• convert Field Service Mobile flows to Data Capture
• audit Field Service Mobile flows
• replace legacy Field Service Mobile flow files
• assess migration readiness

When not to use

• edit an existing Data Capture flow
• author a new Data Capture flow from scratch

Skill page

Source