Migrate from Jobsite Mobile to HighLevel

Jobsite Mobile candidate and applicant records map directly to HighLevel contacts. The candidate's name, email, phone, address, and employment history fields map to the corresponding HighLevel contact fields. The candidate's original create date and last-modified timestamp are preserved as custom datetime fields since HighLevel's native Created Date reflects migration time. Owner resolution happens by email match against HighLevel users.

Jobsite Mobile employer records map to HighLevel companies. Company name, website, industry classification, employee count, and address fields map to their HighLevel counterparts. If the employer has multiple hiring managers in Jobsite Mobile, all related candidates associate to the same HighLevel company via the contact-company relationship. Parent-company hierarchies in Jobsite Mobile map to HighLevel's parent-company relationship if present.

Jobsite Mobile job records have no native equivalent in HighLevel's standard object model. We create a JobListing custom object in HighLevel and map all job-level fields (title, department, location, salary range, employment type, posting date, closing date) as custom fields on the custom object. The custom object is then linked to the Employer company record via a relationship field.

Each Jobsite Mobile application links a candidate to a job. We create a JobApplication custom object in HighLevel with fields for application date, source channel, status (Applied, Screening, Interviewing, Offered, Hired, Rejected), and notes. The application links to the candidate contact and the JobListing custom object. This preserves the many-to-one relationship between candidates and jobs.

Jobsite Mobile's application stage values (Applied, Screening, Interviewing, Offered, Hired, Rejected) map to a HighLevel opportunity pipeline with matching custom stage names. Probability values are assigned per stage — Hired at 100%, Offered at 80%, Interviewing at 50%, Screening at 30%, Applied at 10%, Rejected at 0%. Teams can optionally split the pipeline into multiple HighLevel pipelines if separate hiring tracks need separate views.

Jobsite Mobile interview records map to HighLevel calendar events with original start/end times, invitee list, and location preserved. Interview notes and feedback comments map to HighLevel tasks assigned to the hiring manager contact. The interview type (phone, video, onsite) is stored as a custom field on the calendar event record.

Jobsite Mobile notes attached to a candidate map to HighLevel contact notes. The note body, author, and original create date migrate as the note content, user reference, and a custom datetime field for original creation. Notes are linked to the contact record they belong to in Jobsite Mobile.

Jobsite Mobile employer custom fields — such as billing tier, contract type, or referral source — map to custom fields on the HighLevel company record. We create each custom field in HighLevel before migration and map the values record-by-record. Pick-list custom fields in Jobsite Mobile create pick-list custom fields in HighLevel.

Jobsite Mobile tags and skill labels attached to a candidate map to HighLevel contact tags. Tags are additive — a candidate can carry multiple tags from Jobsite Mobile. Tag names are preserved exactly. Note that HighLevel tags behave differently from Jobsite Mobile tags in workflow triggers; this is surfaced as a gotcha for the team to review post-migration.

When an application reaches the Hired stage in Jobsite Mobile, a placement record is created with hire date, start date, compensation, and placement fee. We map this to a Placement custom object in HighLevel linked to the candidate contact and the employer company. The placement fee and commission data migrate as custom currency fields.

Resume files and supporting documents attached to a candidate application are downloaded from Jobsite Mobile and re-uploaded as file attachments on the corresponding HighLevel contact record. File size limits from HighLevel's storage apply (25MB per file). Inline images in notes are extracted and re-hosted as separate file attachments.

Jobsite Mobile team members who own jobs or applications are matched to HighLevel users by email address. Unmatched owners are flagged before migration — teams either invite them to HighLevel first or assign their records to a designated fallback user. Jobsite Mobile permission roles do not map to HighLevel permission sets and must be reconfigured.