Migrate from Field Pros to Freshsales

Field Pros candidates split by lifecycle stage on migration. Candidates with status 'New' or 'Screening' land as Freshsales Leads; candidates with status 'Offered' or 'Placed' land as Freshsales Contacts. The split preserves recruiting workflow position while respecting Freshsales' separate Lead and Contact objects.

Field Pros clients map 1:1 to Freshsales Accounts on a direct basis. Client billing_model and contract_value migrate as custom fields on the Account record. When multiple Field Pros contacts belong to a single client, those records consolidate into one primary Account with additional contacts represented as Account Contact Relationships, preserving all contact information while maintaining the Freshsales account-centric data model.

Field Pros job orders are recruiting positions, not sales opportunities. We create a custom Position object in Freshsales (via Freshworks developer API) and link it to the Account. Job_order status, employment_type, salary_range, and remote_policy migrate as custom fields on the Position record.

Field Pros placements map directly to Freshsales Opportunities — each placement is a closed or open deal against an Account. Placement_status maps to a custom pick-list field; final placement maps to Closed Won in Freshsales' stage model. Salary, fee_percentage, and fee_amount migrate as custom currency fields on the Opportunity.

Field Pros placement statuses (Open, Interview, Offer, Placed, Rejected) map to a custom Placement_Status__c pick-list field on the Opportunity object. The 'Placed' status maps to StageName Closed Won, while 'Rejected' maps to Closed Lost. Active recruiting stages map to Freshsales pipeline stages based on the migration agreement, preserving the full recruiting lifecycle within Freshsales Opportunity records.

Field Pros recruiter assignments resolve by email match against Freshsales user accounts before migration begins. Any recruiters without matching Freshsales user accounts are flagged for team invitation prior to the migration run. No record lands in Freshsales without a valid OwnerId assignment, ensuring proper ownership and accountability for all migrated recruiting data.

All Field Pros recruiting activities — screening calls, interview rounds, offer conversations — migrate as Freshsales Tasks. Task Type and Subject preserve the activity type. Original timestamps and assigned recruiter OwnerId transfer. Freshsales Tasks attach to the parent Contact or Opportunity record.

Field Pros credential tracking (teacher certifications, EdTech platform credentials) migrates as Freshsales custom objects via the Freshworks developer API entity storage. Credential-to-candidate links migrate as custom lookup relationships. Reporting on credentialed candidates requires Freshsales Pro plan or above, and the custom object schema must be created via the Freshworks developer platform before bulk migration proceeds.

Candidate resumes and credential documents stored in Field Pros re-upload to Freshsales Files, attached to the corresponding Contact or Lead record. Freshsales file size limit of 25MB per file applies. Inline documents in notes are downloaded and rehosted in Freshsales.

Field Pros recruiting workflows — candidate routing rules, stage-advance triggers, and notification automations — do not transfer to Freshsales. FlitStack exports workflow definitions as structured JSON. A Freshsales admin rebuilds equivalent automation using Freshsales Workflows (Pro plan) or Freshsales Journeys (Suite).