Migrate from Jonas Enterprise Service & Construction Software to Zoho CRM

Jonas Customer stores company name, primary contact person, billing address, and trade information in one record. We split this into a Zoho Account for the company entity and a Contact for the primary person, linking them via the Account lookup field. Additional Jonas contact persons for the same customer become additional Zoho Contacts associated to the same Account.

Secondary Jonas contact persons (project managers, field supervisors) attached to a Jonas Customer map directly to Zoho Contacts, linked to the Account created from the parent Jonas Customer record. The email address is used to match against existing Zoho users for owner assignment.

Jonas work orders that represent billable project milestones map to Zoho Deals, preserving job number, phase, cost codes, and budget amounts as custom fields. Work orders representing service incidents or dispatch tickets map to Zoho Cases, preserving dispatch date, technician assignment, and resolution notes. The split is determined by the Jonas work order type field.

Jonas service tickets containing issue descriptions, dispatch timestamps, priority levels, and resolution outcomes map to Zoho Cases. The original Jonas ticket number is stored in a custom field (Jonas_Ticket_ID__c) to preserve traceability. Technician assignments are resolved by matching the Jonas technician email to a Zoho user account; when no match exists, the assignment is kept as a contact reference or flagged for review, ensuring every case has an identifiable owner.

Jonas PMAs (contract scope, visit frequency, billing terms) have no native Zoho CRM equivalent. We create a custom Zoho module called PMA_Agreement__c with fields for contract start/end dates, service frequency, and billing method. The custom module links to the Account and associated Contacts.

Jonas job cost records with cost codes, phase budgets, and WIP percentages map to custom fields on the corresponding Zoho Deal (Cost_Code__c, Phase__c, WIP_Flag__c). Detailed cost breakdowns are attached as Notes or file attachments on the Deal record. Direct cost-code-to-Zoho-field mapping is not 1:1 due to structural differences.

Jonas project schedules with milestones map to a Zoho Deal as the parent record, with milestones represented as Zoho Tasks linked to the Deal. Original milestone names and target dates are preserved in Task subject and due date fields. Project manager assignment resolves by email match to the Zoho user who should own the Deal.

Jonas documents (drawings, contracts, photos) attached to customers or work orders are downloaded and re-uploaded to the corresponding Zoho Account, Contact, Deal, or Case record as file attachments. Zoho's 25MB per-file limit is enforced; files exceeding this are noted for manual retrieval.

Jonas employees who are CRM-relevant (project managers, service coordinators) are matched to Zoho Users by email for owner assignment. Field technicians without Zoho user accounts are migrated as Contacts in a private Team module so service tickets can reference them by name without creating user licenses.

Jonas inventory items used on work orders map to Zoho Products. Product name, SKU, unit price, and description transfer directly. Inventory quantities are not migrated as Zoho Products stores pricing and description, not stock levels — a separate inventory integration handles real-time quantities post-migration.

Jonas payroll records, labor costing entries, and union payroll tier data are accounting module content outside the CRM scope. These records are not migrated to Zoho CRM. If labor reporting is needed in Zoho, a custom Labor_Entry__c module can be created as a reference archive, but operational payroll remains in Jonas or a dedicated payroll tool.

Jonas change orders linked to jobs map to the corresponding Zoho Deal as a custom field set: Change_Order_Number__c, CO_Amount__c, CO_Status__c, and the change order document attached as a file. The Deal amount is not automatically incremented; the CO impact is noted for manual or workflow-based update.