Migrate from ServiceMax to Zoho CRM

Billable ServiceMax work orders map to Zoho Deals. Each Deal stores the work order name, total service revenue (Amount), and the service address as a custom text field. Original SVMXC__Created_Date__c is preserved as Service_WO_Create_Date__c since Zoho sets Created_Time at migration. Work order status maps value-by-value to Zoho StageName.

Work orders that represent warranty claims or no-charge service rather than billable revenue route to Zoho Cases. The Case Subject carries the Work Order Name, and the Case Reason field holds the original work order type. SVMXC__Priority__c maps to the Case Priority pick-list value-by-value.

Installed products lack a native Zoho equivalent. We create a custom Installed_Products custom module. The customer's Account links to the installed product record. Serial number, product model, and installation date become custom fields on the Installed_Products module. Customer-facing asset names map to the Account Name for quick lookup.

Service contracts require a custom Zoho CRM module. Contract name, start and end dates, total contract value, and contract type (Full Coverage, Time-and-Materials, etc.) migrate as custom fields. Covered assets link to the custom Installed_Products module via a multi-select lookup subform in Zoho's structure.

Entitlements — which define billable vs. covered work under a contract — merge into the Service_Contracts custom module as a Billable_Coverage__c pick-list and Covered_Service_Type__c multi-select field. Each entitlement's coverage terms become a sub-record within the associated contract rather than a standalone object.

Service appointments map to Zoho Events. The appointment start time migrates as Event Start_DateTime, the technician assigned to the appointment links to the Zoho User via email-match on SVMXC__Technician__c. Site address migrates as Event Location. Original appointment status maps to Zoho Event Status.

ServiceMax Contact records map one-to-one to Zoho Contacts, preserving all standard fields such as First_Name, Last_Name, Email, Phone, and Mailing_Street. Custom fields on the Contact object also migrate as Zoho custom fields, and the Primary Account link is resolved by matching SVMXC__Company__c to the target Zoho Account. Duplicate detection uses Email as the unique key, and any unmatched contacts are flagged for review before import.

ServiceMax Account records map one-to-one to Zoho Accounts, carrying over all standard fields including Account Name, Billing Address, Shipping Address, Industry, Annual Revenue, and Number of Employees. Custom fields on the Account object also transfer as Zoho custom fields, and Parent Account hierarchies defined by SVMXC__Parent_Account__c are preserved by linking to Zoho's Parent_Account lookup. Duplicate detection uses a combination of Account Name and Billing City to identify matches before import.

ServiceMax product catalog maps directly to Zoho Products, transferring standard fields such as Product Name, Product Code, Unit Price, Product Category, and Description. Custom fields defined in ServiceMax also migrate, and each product links to related parts so work order line items in Zoho reference the correct inventory. During migration validation, the system cross-checks part numbers from work orders against imported product records to ensure consistency.

Parts requests (internal inventory pull requests tied to work orders) translate to Zoho Purchase Orders or a custom Parts_Request module depending on whether your Zoho instance includes Inventory Management. Each parts request line references the work order Deal and the product.

Meter readings and counter data from installed products—such as usage hours, page counts, or cycle counts—require a custom Meter_Readings module in Zoho CRM linked to the Installed_Products module via a lookup. Each reading stores the reading date, counter value, and a reading type pick-list (e.g., Hourly, Monthly, Event) as custom fields. The module can also tie to service contracts or work orders for usage‑based billing and maintenance planning.

SFM Transactions, SFM Wizards, Mobile Configs, Dispatch Console Views, Counter Rules, and SPM Calculation Methods are Force.com-native declarative configuration items with no Zoho CRM equivalent. FlitStack exports these definitions as JSON reference files for your Zoho admin to use when rebuilding in Blueprint.