Migrate from WennSoft to Zoho CRM

This migration uses a direct 1:1 mapping approach where WennSoft Customers with a designated primary location translate directly into Zoho Accounts, with the primary location address stored in the standard Account Address fields. Parent-company hierarchies maintained in WennSoft map to Zoho's native Account Hierarchy feature, preserving organizational structure.

WennSoft allows N locations per customer. Zoho Accounts store one primary address. Each additional location creates either a separate Account record in the Account Hierarchy or a custom Location subform on the Account — your admin chooses the model before migration. Location-specific equipment lists follow the chosen location structure.

This migration applies a direct field-to-field mapping where standard WennSoft contact attributes including name, phone, email, and job title translate directly to their corresponding Zoho Contact standard fields. The contact-to-location associations maintained in WennSoft automatically become Zoho Contact-to-Account lookup relationships upon migration. Multiple contacts assigned to a single location each migrate as individual 1:1 records preserving all original data.

Equipment has no native Zoho CRM equivalent. FlitStack creates a Zoho custom module named Equipment with fields for Serial Number, Model, Manufacturer, Contract Type, Warranty End Date, and a lookup to the parent Account. Equipment-to-location relationships migrate as lookup relationships in the custom module.

Service calls become Zoho Deals. The call type (Repair, Maintenance, Installation) migrates as a custom pick-list field (Call_Type__c). Problem type, priority, and billing rate migrates as custom fields on the Deal. Original call-open and call-close timestamps are preserved as custom datetime fields for service history continuity.

WennSoft work orders attached to a service call merge into the Zoho Deal as custom subform rows capturing work order number, assigned technician, labor hours, and material cost. Each work order row is stored in a Work_Order_Subform custom field on the Deal — no separate Zoho module required unless your team needs standalone work order reporting.

All WennSoft quotes are systematically mapped to Zoho Quotes and linked to their corresponding Deals, maintaining the relationship between estimates and opportunities. Line items including labor rates, parts, and service types translate directly to Zoho Quote Line Items using existing Zoho Products as the item catalog. Quote status values such as Open, Accepted, and Declined map precisely to Zoho Quote Stage values for consistent pipeline reporting.

Invoiced service calls from WennSoft are converted into Zoho Invoices, each properly linked to its parent Deal to maintain relationship integrity. Key billing information including total amount and invoice number map directly to their corresponding Zoho Invoice fields. WennSoft-specific invoice terms and payment status indicators migrate as custom fields on the Zoho Invoice record for complete financial traceability.

WennSoft time entries (technician, hours, labor rate, cost) attached to a work order are stored as a custom subform on the Zoho Deal or as Task records with custom labor fields. Zoho's standard time-tracking module is a separate product (Zoho FSM) — time entries migrate as structured data rather than native time records.

WennSoft service contracts and warranty records have no Zoho equivalent. A custom Contracts module is created with fields for Contract ID, Account, Equipment, Start Date, End Date, Contract Type, and Coverage Terms. Contracts are linked to the relevant Account and Equipment records via lookup relationships.

Service call attachments, equipment photos, and work order documents are downloaded from WennSoft storage and re-uploaded as Zoho Files attached to the corresponding Deal or Equipment record. File size limit of 20MB per file applies — large files are flagged for manual handling.

WennSoft technicians and dispatchers are matched to Zoho Users by email address. Unmatched users are flagged before migration. Zoho User IDs are required for Deal Owner, Task Owner, and Event Owner assignments — this resolution step happens before data loads begin.