Migrate from Planado to Zoho CRM

Planado jobs map directly to Zoho CRM Tasks. The Planado job title becomes the Task Subject, description maps to Comments, status maps to Zoho Status (Open / Overdue / Completed), priority maps to Priority, and the assigned technician resolves to the Task Owner by email match. Original job create date is preserved as a custom datetime field since Zoho's CreatedDate reflects migration-run time.

Planado job site address, latitude/longitude, and routing data have no native Zoho CRM equivalent. FlitStack maps address lines to Task's Where field (if enabled) or stores them in custom fields (Job_Site_Address__md, GPS_Latitude__c, GPS_Longitude__c). The raw GPS trace is not portable — site coordinates migrate as a point-in-time snapshot for reference.

Planado checklist items and their responses are key-value pairs per job. Each distinct checklist item that appears across jobs generates a custom pick-list or multi-line text field in the Zoho Task module (e.g., Safety_Check_Completed__c, Parts_Used__c). Responses are written as field values. If a checklist has more than 50 distinct items, FlitStack may consolidate responses into a structured JSON or multi-line text field to stay within Zoho's 300-field-per-module limit.

Photos and documents attached to a Planado job are downloaded and re-uploaded as Zoho CRM Task attachments via the Attachments API. File size limits apply per Zoho tier (25MB default per file). Inline images in checklist notes are extracted, downloaded, and attached to the corresponding Task record with a reference note.

Planado clients with company name and address map to Zoho CRM Accounts. Client name becomes Account Name, domain/website maps to Website, address fields map to Billing Street/City/State/Postal Code. If the Planado client is an individual (sole proprietor), it may map to both an Account and a Contact — FlitStack creates both records and links them.

Named contacts stored on a Planado client map to Zoho CRM Contacts. First name, last name, email, phone, and job title map directly to Contact fields. The Contact is linked to the parent Account (from the Planado client record) via Account Name lookup. FlitStack resolves the Account record first so the Contact.AccountId foreign key resolves correctly during import.

Planado field workers are user profiles, not contact records. FlitStack matches each Planado worker email to an existing Zoho CRM User by email. If a Zoho User does not exist, the worker record is flagged for your admin to create first — FlitStack will not create Zoho Users. Workers without a Zoho User are assigned to a fallback Owner designated before migration.

Planado's scheduling and availability windows have no Zoho CRM equivalent. FlitStack exports availability data as a structured text note attached to the corresponding User record. Zoho FSM or a third-party scheduling tool handles this post-migration — FlitStack provides the rebuild reference.

Planado routing logic (which worker gets assigned to which job type or zone) is internal to Planado and not exposed via API. This cannot be migrated. FlitStack exports a configuration summary document describing your routing rules so your Zoho admin can rebuild them as Zoho Flow workflows or assignment rules post-migration.

Planado SMS and email notification templates (e.g., ' technician en route', 'job completed') do not export in a portable format. FlitStack documents the trigger conditions and message templates from Planado so your Zoho admin can recreate them in Zoho CRM's email templates and Zoho Flow notification actions.

Any custom properties on Planado jobs beyond the standard fields (e.g., Contract_Type__c, Service_Level__c) map to Zoho CRM custom fields on the Task module. FlitStack creates these fields during schema setup and maps values directly or via value mapping if the custom property is a pick-list with restricted values.

The Planado internal job ID is stored as Source_System_ID__c on every migrated Task. This field enables delta-run de-duplication (if the same Planado job ID appears in a subsequent export, FlitStack updates rather than re-creates the record) and provides traceability for reconciliation.