Migrate from Fieldy to Zoho CRM

Fieldy customers migrate to Zoho Contacts. Each customer record carries name, email, phone, address, and custom properties. Primary company association in Fieldy maps to Contact.Account lookup in Zoho. Customer type or tags become custom pick-list fields in Zoho. During migration, we validate that email addresses are unique to prevent duplicate contact records in Zoho.

Fieldy company records map 1:1 to Zoho Accounts. Company name becomes Account Name. Website, industry, employee count, and annual revenue map to matching Zoho standard fields. Parent-company hierarchy in Fieldy maps to Account.Parent_Account lookup in Zoho. If a parent company is missing, we create a placeholder Account and flag it for your team to resolve after migration.

Fieldy job records are the primary translation challenge. The job name maps to Deal Name, job amount maps to Deal Amount, and Fieldy job status (e.g., Scheduled, In Progress, Completed) maps to Zoho Deal Stage values via value mapping. Fieldy job priority migrates as a custom pick-list field on the Zoho Deal. Site address and service type are preserved as custom fields on the Deal record.

Fieldy technician assigned to a job resolves by email match to a Zoho User record. The matched User becomes the Deal Owner in Zoho CRM. Unmatched technicians are flagged before migration; your team assigns them to Zoho users first. This ensures every Deal has a responsible owner and adheres to Zoho's sharing rules for record visibility across your organization.

Fieldy job line items (parts, labor, materials) migrate as Zoho Deal Line Items linked to the Deal. Product records in Fieldy map to Zoho Products with SKU, unit price, and description. If Fieldy products have no SKU, Zoho product records are created with a generated identifier.

Fieldy invoices migrate to Zoho Invoices when the Professional tier or higher is active. Invoice number, date, due date, line items, tax, and payment status map directly. If the Zoho plan does not include the Invoice module, invoices migrate as custom fields on the Deal with the invoice data preserved for reference.

Fieldy staff and technician records map to Zoho Users. First name, last name, email, phone, and role title map to matching Zoho User fields. Active/inactive status in Fieldy controls the Zoho User active flag. Admin and technician roles in Fieldy require manual review against Zoho role and profile assignments.

Fieldy job attachments — including customer signatures, photos, and job documents — re-upload as Zoho Attachments linked to the corresponding Deal record. Zoho supports up to 25MB per file via its Files module. Inline images in job notes are downloaded and rehosted in Zoho's Documents.

Any Fieldy custom property on a customer record that has no Zoho standard field equivalent requires a Zoho custom field created before migration. We deliver a custom field creation plan specifying field label, API name, data type, and pick-list values where applicable.

Fieldy job-specific custom properties (e.g., service type categories, warranty codes, site-specific notes) map to Zoho Deal custom fields. Multi-select values in Fieldy custom properties may require custom multi-select fields in Zoho, which are supported up to the 300-field module limit.

Fieldy job activity logs and internal notes migrate as Zoho Notes attached to the Deal. Timestamps and the technician who added the note are preserved. If Fieldy logs specific action types (e.g., site visit, Parts ordered), those can map to Zoho Tasks with Type field for reporting clarity.