Migrate from Field Pros to HighLevel

Automation rebuild is mandatory — no automated export of trigger-action logic

FieldPros candidate workflows and placement-stage-triggered automations (interview scheduling notifications, stage-change alerts, recruiter assignment rules) use an internal automation model that has no export format compatible with HighLevel's Workflows engine. HighLevel Workflows run on triggers (contact created, opportunity stage changed, form submitted) with action chains, conditions, and delays. Every automation in FieldPros must be documented, mapped to a HighLevel trigger, and rebuilt manually. FlitStack AI exports the automation definitions as a structured reference document your HighLevel admin uses to rebuild them. This is the single largest post-migration effort for most FieldPros-to-HighLevel migrations and should be scoped separately from the data migration timeline.

Pipeline stages must be pre-created in HighLevel before Opportunities migrate

HighLevel does not create pipeline stages dynamically during import — Opportunities require a valid Pipeline and Stage assignment at creation time. If your FieldPros setup has 7 placement statuses (Applied, Screening, Phone Screen, Technical Interview, Final Interview, Offer, Placed), all 7 must exist as HighLevel Pipeline stages before any Opportunity record can be created. FlitStack AI delivers a pipeline-setup checklist as part of the pre-migration plan. Probability percentages, forecast category assignment, and any stage-specific automation triggers must be configured in HighLevel's Pipeline settings before data lands.

HighLevel's sub-account architecture changes how multi-client workspaces are organized

If your FieldPros account manages placements for multiple EdTech client organizations from a single login, HighLevel's equivalent structure is sub-accounts — isolated workspaces under your agency org, each with its own contacts, pipelines, tags, and workflows. Migrating multiple client workspaces from FieldPros means migrating into multiple HighLevel sub-accounts rather than into one consolidated HighLevel org. Sub-account provisioning must happen before migration, and each sub-account needs its own pipeline configuration. This architectural difference affects the migration scoping significantly and can extend timeline by 1–2 weeks if pre-provisioning is not done in parallel.

Tag-based segmentation in FieldPros does not automatically become HighLevel SmartLists

FieldPros tags encoding candidate skills, sourcing channels, and qualification tiers migrate as HighLevel Tags, but HighLevel's SmartList segmentation operates on filter conditions — not tag rollups. For example, a FieldPros tag combination like 'Python+Mid-Level+Remote' identifying a candidate segment must be recreated in HighLevel as a SmartList with three separate tag-filter conditions (Tag contains Python AND Tag contains Mid-Level AND Tag contains Remote). HighLevel Tags are OR-filtered by default in SmartLists unless you configure AND logic explicitly. FlitStack AI surfaces all unique tag combinations from FieldPros so your admin can decide which segments to rebuild as SmartLists versus which to collapse into fewer, more actionable tags.

API rate limits on HighLevel sub-accounts constrain migration batch sizing

HighLevel API 2.0 enforces rate limits per sub-account: Sub-account A (GHL-APP) allows 200,000 requests per day and 100 requests per 10-second burst. Sub-account B and lower tiers have lower daily limits. High-volume migrations with hundreds of thousands of records use batched API calls that must stay within these limits. FlitStack AI manages queue throttling automatically, but extremely large record sets may require extended migration windows or staged migration runs. Historical archive records can be migrated in a second pass after live records are in HighLevel.