Migrate from FRONTU to Zoho CRM

Frontu Customers (service-location entities with primary contact info) map to Zoho Accounts for the company record and a primary Contact for the service manager or site contact. Frontu's customer name becomes Account Name; the contact name, phone, and email become the Contact record. If Frontu stores multiple contact roles per customer, secondary contacts are added as related Contact records.

Frontu Jobs (field service tasks with status, location, and assignment) translate to Zoho Deals representing each service event. Job name becomes Deal Name; Job status (Pending, In Progress, Completed) maps to Zoho Stage values. If your team uses custom job types or service categories, we create a custom Jobs module with _C suffix and map those fields to custom pick-list and multi-select fields in Zoho.

Frontu Employees (technicians) resolve to Zoho Users by email matching. Frontu's employee name, email, phone, and availability status migrate as User fields. Zoho's User record is the destination for technician ownership of Deals, Tasks, and Events. Unmatched employees are flagged before migration; your Zoho admin creates the User records and we remap by email.

Frontu Activity Logs (check-in, check-out, photos, signatures, notes) become Zoho Tasks (for discrete action items like 'Completed inspection') or Events (for scheduled site visits with start/end times). Original timestamps, technician owner, and parent Job reference are preserved. Photos and signatures are downloaded and re-uploaded as Zoho Attachments linked to the corresponding Deal or Task.

Frontu service locations with GPS coordinates, site name, and address details map to Zoho Account address fields (Street, City, State, Zip, Country). If your Frontu setup tracks multiple locations per customer with distinct site managers, we create a custom Locations_C module linked to Account for N:1 relationships. GPS coordinates migrate as custom latitude/longitude decimal fields.

Frontu job checklists (items, steps, completion status per job) have no native Zoho equivalent. We migrate each checklist item as a separate custom field on the Deal or custom Jobs_C module: either multi-select pick-lists for simple pass/fail items or long-text fields for itemized notes. Your Zoho admin can restructure these into sub-forms after migration if Zoho forms support is available in your tier.

Frontu tracks job status transitions with timestamps. Zoho Deal history is tracked via the Audit Log, but original status-change timestamps are not surfaced on the record. We preserve each status transition as a pair of custom datetime fields (e.g., Status_In_Progress_Date__c, Status_Completed_Date__c) on the Deal for reporting continuity.

Frontu file attachments (photos, PDFs, signed forms) on Jobs and Activity Logs are downloaded and re-uploaded to Zoho. Attachments are linked to the corresponding Deal or Task record. Zoho supports files up to 25 MB per attachment. Inline images from Frontu Activity Logs are extracted and hosted as Zoho Attachments.

Frontu custom fields on Jobs (e.g., Equipment ID, Service Type, Warranty Code) map to custom fields in Zoho. Data type matching is performed: text to varchar, numbers to integer/decimal, dates to datetime. Pick-list values from Frontu are recreated as Zoho pick-list values. We create the custom fields in Zoho via API before the migration run so data lands in the correct schema.

Frontu technician teams or dispatch groups map to Zoho Territories. Territory assignment in Zoho controls data visibility for users. We map team membership to territory membership so each technician sees only their assigned Accounts and Deals. If your Frontu setup uses regions or service areas, those become Zoho Territories linked to the relevant Accounts.

Frontu invoices or billing records tied to completed jobs have no direct CRM equivalent. We export them as reference records linked by Deal ID for import into Zoho Books or as a custom Invoice_C module. If you use Zoho Books, the Deal ID cross-reference allows your accounting team to match invoices to service events post-migration.