Migrate from ServiceTracker to Zoho CRM

Work order hierarchy flattens into a flat Deal pipeline with no native sub-task structure

ServiceTracker work orders can have sub-tasks (e.g., a preventive maintenance visit with multiple inspection steps each tracked separately). Zoho CRM Deals are single records with no native sub-task hierarchy — there is no sub-Deal or task-within-Deal structure equivalent to ServiceTracker's sub-work-order model. When ServiceTracker sub-tasks exist, we consolidate them into the parent work order's description field as a bulleted list, or we create Zoho Tasks linked to the Deal via the Related To lookup. This means the granular sub-task status is not individually visible on the Deal record without opening the related Tasks list. Teams relying on sub-task-level reporting in ServiceTracker will need to build Zoho Analytics reports that roll up related Tasks — this is a post-migration configuration step.

Zoho API credit budget constrains migration throughput for large record volumes

Zoho CRM API v8 deducts credits per operation: insert/update/upsert costs 1 credit per 10 records. Enterprise plans provide 50,000 + (users × 1,000) credits per day, capped at 1,000,000. For a migration with 50,000 work orders, 30,000 contacts, and 20,000 assets, the daily credit consumption during bulk insert can exceed the daily budget on Standard or Professional tiers, requiring the migration to run in batches across multiple days. We calculate the credit budget from your Zoho edition before migration starts and throttle API calls to stay within the daily limit. If your migration would exceed the Enterprise daily cap, we request a credit top-up add-on from Zoho or run the migration during off-peak hours to avoid daytime consumption conflicts.

Dispatch scheduling and technician territory rules have no Zoho CRM equivalent

ServiceTracker's core differentiator is its scheduling engine — it matches technicians to work orders based on territory, skill set, and real-time availability. Zoho CRM has no native scheduling, dispatch, or territory-management module. Technician assignment on migrated work orders becomes a static Contact lookup on the Deal — the dynamic re-assignment, availability checking, and route optimization that ServiceTracker provides are lost. Post-migration, teams need either Zoho FSM (a separate product), a third-party scheduling integration, or a custom Deluge script that replicates the territory-matching logic. We document the ServiceTracker assignment rules as part of the migration artifacts so your Zoho admin can reference them when rebuilding dispatch logic.

Customer portal login credentials do not transfer — access must be re-provisioned

ServiceTracker customer portal accounts (separate login credentials, portal permissions, and customer-specific portal settings) are stored in ServiceTracker's authentication system and have no equivalent in Zoho CRM's portal framework. The portal contact records migrate as Zoho Contacts, but portal login credentials, password reset policies, and portal-specific configuration do not transfer. After migration, Zoho portal access must be re-created for each customer. We export the portal username list from ServiceTracker as a CSV and provide a portal-provisioning checklist so your Zoho admin can set up Zoho Customer Portal access before go-live.

ServiceTracker's Open status maps to multiple Zoho Deal Stages — stage mapping ambiguity

ServiceTracker work order status is a flat pick-list: Open, In Progress, On Hold, Completed, Invoiced. Zoho Deal Stage is a per-pipeline pick-list that typically includes stages like Qualification, Needs Analysis, Proposal, Negotiation, Closed Won, Closed Lost. There is no 1:1 mapping between these two taxonomies — for example, ServiceTracker's single 'Open' status must be interpreted as Qualification or Needs Analysis depending on business context. We surface this ambiguity before migration runs and ask your team to define the Zoho stage each ServiceTracker status value should represent. Without this input, we apply a conservative default mapping that routes Open to the earliest non-closed stage in your Zoho pipeline.