Migrate from Jobsite Mobile to Zoho CRM

Jobsite Mobile stores all contacts in one list. Zoho CRM separates Leads (prospects not yet qualified) from Contacts (active accounts). FlitStack routes contacts by a status flag — if no status exists, all records land as Zoho Leads by default, and your team can convert them individually.

The Jobsite Mobile Company object maps 1:1 to the Zoho CRM Account module. Parent‑company relationships in Jobsite Mobile migrate as the Parent Account lookup in Zoho, provided the parent record is processed first in the migration sequence. The mapping also preserves the original company identifier and any custom fields defined on the Company object, so all attributes transfer into Zoho's Account record.

Jobsite Mobile deal or project records map to the Zoho CRM Deal module. Pipeline stages in Jobsite Mobile map to Zoho Deal Stage values. If Jobsite Mobile uses multiple named pipelines, each pipeline requires its own stage set in Zoho under the Deals module before mapping can proceed.

Jobsite Mobile tasks migrate as Zoho CRM Tasks. Subject, due date, status, and priority transfer directly. Owner is resolved by email match to Zoho users. Open and completed statuses map to Zoho's Not Started, In Progress, and Completed values. If a Jobsite Mobile task references a parent contact or deal, the migration links the Zoho Task to the corresponding Zoho record using the parent lookup field, preserving activity context.

Jobsite Mobile events with start/end timestamps and attendees map to Zoho CRM Events. Recurring events export from Jobsite with all instances expanded; Zoho stores recurring events as a master event with recurrence rules. The migration converts timestamps to the target Zoho time zone, and any attendee email addresses are added to the Zoho Event's invitee list to preserve the original meeting roster.

Jobsite Mobile notes migrate to Zoho CRM Notes attached to the corresponding parent record (Account, Lead, Contact, or Deal). Rich-text formatting is preserved as HTML where Jobsite Mobile supports it; plain-text notes import without transformation. If a note includes an @mention of a user or a tag, the migration retains the mention text so your team can re‑link it manually in Zoho.

Jobsite Mobile call logs with duration, outcome, and timestamp become Zoho Tasks with Type = Call. Email activity records migrate as Tasks with Type = Email. If Jobsite Mobile stores email body content, it transfers to the Task description field in Zoho.

Jobsite Mobile owner IDs have no Zoho equivalent — they are platform-specific integers. FlitStack resolves each owner by matching the email address stored on the source record to an active Zoho user. Unmatched owners are assigned to a designated fallback Zoho user and flagged for review before the migration commits.

Jobsite Mobile custom objects migrate as Zoho CRM Custom Modules. The source custom object's API name is preserved as the Zoho module's API name. Custom module records, their fields, and relationships to standard modules transfer. N:N relationships require a linking module creation in Zoho before the migration runs.

Jobsite Mobile file attachments re-upload to Zoho CRM as record attachments. The attachment is linked to the same parent record type it was attached to in Jobsite Mobile. File size is validated against the target Zoho plan's limit (10 MB Free, 50 MB Professional+); oversized files are flagged for manual handling.

Jobsite Mobile subforms or line-item structures within deals map to Zoho Deal subforms. Each row of the subform becomes a subform entry in Zoho, linked to the parent Deal record. Field types (currency, date, lookup) are matched to their Zoho equivalents during the field-mapping phase.

Jobsite Mobile workflows, automations, and approval rules do not transfer to Zoho CRM. FlitStack documents your existing automation definitions in a rebuild reference document so your Zoho admin can recreate them using Blueprint, workflow rules, or Deluge scripts in Zoho.