Migrate from Accruent Vx Field to Zoho CRM

Vx Field dispatch rules and scheduling logic have no Zoho CRM equivalent

Accruent Vx Field encodes intelligent scheduling rules — travel-time optimisation, technician skill matching, SLA deadline calculation, and priority-based auto-dispatch — as platform-native configurations. Zoho CRM has no equivalent scheduling engine. When migrating, FlitStack AI preserves the scheduled date, assigned technician, priority, and SLA fields on the Work_Order__c record. The scheduling logic itself must be rebuilt in Zoho using Blueprint for stage-based flows and Deluge functions for any algorithmic dispatch logic, a step that requires a Zoho administrator or consultant and is scoped separately from the data migration.

Parts bin locations and multi-warehouse inventory require custom fields in Zoho Products

Vx Field tracks parts by warehouse location and bin number, supporting multi-site inventory with separate stock counts per site. Zoho's standard Product module holds a single unit price and stock quantity without warehouse scoping. Migrating a multi-warehouse parts inventory requires creating custom fields on the Product record — Bin_Location__c, Warehouse__c, Stock_Qty_Warehouse_A__c, and so on — for each warehouse. We create these fields during the schema-prep step, but the admin must decide on the warehouse naming convention and confirm whether lot or serial number tracking is required before the full import runs.

Technician email resolution is required before work order records can own an OwnerId

Zoho CRM assigns records to User accounts, not to arbitrary contact records. Vx Field technician records identified by internal ID must be matched by email to a Zoho User before Work_Order__c records can carry an OwnerId. If the migration runs before the technician roster is confirmed in Zoho, unmatched OwnerId values default to the admin user or remain blank, creating orphaned assignment data. FlitStack AI delivers a pre-migration technician resolution report listing every Vx Field technician, their email, and their Zoho User match status so the admin can create missing Zoho User accounts before the migration commits.

Zoho's bulk API credit system imposes throttling on large-volume imports

Zoho CRM deducts API credits per operation, with limits varying by plan tier: 500 requests per minute for Standard, 2,500 for Professional, and 10,000 for Enterprise, plus a 24-hour rolling window cap. A migration of 200,000 work order records with multiple custom fields and attachments can consume significant API credits within a short window. FlitStack AI paces imports using Zoho's batch endpoints and respects per-minute rate limits for the target plan tier. If the source account is on a lower Zoho tier, FlitStack will split the load into staged batches to avoid 429 errors and credit exhaustion.

Attachments stored as inline images in Vx Field require format conversion for Zoho Files

Vx Field work orders sometimes store photos and inspection images as inline attachments embedded in rich-text fields rather than as discrete file records. Zoho Files require re-uploading attachments as separate file entities attached to the parent record. FlitStack AI extracts inline image data, downloads each file, and re-uploads it as a named Zoho File with a reference link back to the Work_Order__c record. If the inline image is in a proprietary Vx Field format, FlitStack converts to PNG or JPEG during the extraction step. Any conversion failures are logged and surfaced in the post-migration validation report.