Migrate your FieldPro data

FieldPro organizes data under a single Organization entity per tenant. Export yields the org-level configuration including settings, time zones, and currency preferences. No multi-org or sub-org hierarchy is present in the standard data model.

Every active mobile user requires a FieldPro license. We export all user records including role assignments, but we flag any records where last_active_date predates the migration window — these users may represent unused licenses rather than active personnel.

Outlets are the primary spatial entity in FieldPro, capturing outlet name, GPS coordinates, address, and outlet type. Unique attributes like outlet codes can serve as primary keys for deduplication during import.

A Visit records a field employee's encounter with an Outlet at a specific timestamp. Each Visit carries GPS coordinates, outlet reference, user reference, and completion status. We preserve the visit-outlet linkage and the chronological sequence of visits per route.

Routes group Visits into scheduled sequences for field employees. Route-level data (route name, scheduled date, assigned user) is exported alongside its child Visits. Some route configurations reference custom field logic that requires field-level mapping.

The product catalog includes SKU, name, category, and pricing. Products are referenced by Orders and can carry custom fields. We preserve the full product list as a lookup table before importing order line items.

Orders are created during or after a Visit and reference the outlet, user, and products. Order status (draft, submitted, confirmed) is preserved. Order-level custom fields are mapped to the destination schema.

Tasks represent action items assigned to field users, often tied to specific outlets or routes. Custom task fields and task-type configurations require mapping to the destination system, as FieldPro task schemas vary by deployment package.

Visit attachments include photos (from FieldPro Detect shelf audits), signatures, and documents. We export binary blobs with metadata. Detected image metadata (shelf compliance flags) is exported as structured JSON alongside the image file.

FieldPro supports custom fields on Outlets, Visits, Orders, and Tasks. Custom field definitions (field type, required flag, picklist values) are exported separately from data rows and mapped to equivalent destination fields.

ERP sync (Business Central, NetSuite, Sage CRM, SYSPRO) is configured per organization. Migration requires re-establishing these connections on the destination platform, including re-mapping account codes and product IDs.