Migrate from FieldFX to Zoho CRM

FieldFX Account maps directly to Zoho CRM Accounts module. Zoho Accounts support parent-child hierarchies via the Parent Account lookup field, matching Salesforce Account.ParentId behavior. Custom address fields on the Account object — including Billing Street, City, State, and Country — map to corresponding Zoho address fields. Industry pick-list values require explicit value mapping because Zoho's industry taxonomy differs from Salesforce's, and any unmatched values default to the nearest equivalent Zoho pick-list entry before import.

FieldFX Contact maps to Zoho CRM Contacts module. The primary Account is assigned via the Account Name lookup in Zoho — this is a critical dependency because the Account record must be migrated first so the lookup relationship resolves correctly during the Contact import phase. All standard Contact fields including name, email, phone, and mailing address map directly to their Zoho equivalents without transformation.

Zoho CRM does not have a standalone Asset object in all editions; assets can be stored as records in the Accounts module with a custom Asset-related pick-list, or as a separate custom module if Zoho Inventory is licensed. FlitStack AI maps Asset records to whichever structure matches your Zoho plan and creates the necessary fields during the pre-migration schema setup phase.

FieldFX Ticket (SVMX_VF_Ticket__c) becomes a Zoho custom module named Tickets. All Ticket custom fields map to Zoho custom fields on that module. The ticket's related Account and Contact are mapped via Zoho lookup fields pointing to the migrated Accounts and Contacts records. Status and Priority pick-list values require explicit value mapping to ensure the Zoho Ticket Status field reflects the same business states as the original FieldFX configuration.

FieldFX Job (SVMX_VF_Job__c) migrates as a Zoho custom module named Jobs. Job records are linked to their parent Ticket via a Zoho lookup field once both modules exist in Zoho. Scheduling and dispatch fields map to Zoho custom datetime and user fields. Job Status pick-list values require pre-import configuration in Zoho to ensure the migration does not fail on unmatched status values.

Ticket Item records map to a Zoho custom module Ticket Items with a lookup to the parent Ticket. The Extended Amount formula field (quantity × rate) is stored as a numeric field in Zoho since Zoho does not replicate Salesforce formula field evaluation during import — the value is computed before the import CSV is generated. This ensures the computed total is preserved without requiring Zoho custom functions for line-item arithmetic.

FieldFX Problem records (SVMX_VF_Problem__c) migrate as a Zoho custom Problems module. Each Problem links to its parent Ticket via a Zoho lookup. Custom fields on Problem — such as priority, cause code, and resolution — map to Zoho pick-list and text fields. The N:N relationship between Tickets and Problems uses a linking module in Zoho, created after both parent modules have fully committed to avoid orphaned relationships.

Service Contract records map to a Zoho custom Service Contracts module. Coverage start and end dates migrate as Zoho date fields. Contract type and billing terms migrate as pick-list fields configured to match FieldFX values. Contract line items link to their parent contract via Zoho lookups. The module structure is created before migration using the Zoho CRM Fields API endpoint, ensuring all field types are ready before data import begins.

FieldFX owner assignment (OwnerId) resolves by email match against Zoho CRM Users list. This is a direct email-to-email resolution step that requires Zoho user accounts to exist before migration runs. Unmatched owner IDs are flagged in a pre-migration report; your team either creates Zoho user accounts for those owners before the migration begins or designates a fallback Zoho user to own those records.

Salesforce Files and Attachments linked to Ticket, Job, or Account records are downloaded via the Salesforce API and re-uploaded to Zoho CRM Attachments linked to the corresponding Zoho record. File size limits apply per Zoho edition and storage quota; large files exceeding CRM attachment limits may require Zoho Docs integration for storage. The attachment migration runs after all parent records have been committed to ensure lookup relationships resolve correctly.

FieldFX calendar events (SVMX events on Job or Ticket) migrate as Zoho Events with original start time, end time, and assigned technician preserved. The related Ticket or Job lookup is restored via the migration ID chain established during the pre-migration phase. Event records without a resolvable parent are flagged for manual review after migration completes. Duration is calculated from start and end datetime values captured at extraction time.

FieldFX task records — service completion notes, dispatch updates, and status change logs — migrate as Zoho Tasks linked to the parent Ticket or Job record. Original subject, status, and due date are preserved. Owner assignment follows the email-match resolution step used for all other objects. Task priority values require pick-list mapping if FieldFX uses custom priority configurations not present in Zoho's default Task priority set.

FieldFX Status Workflow definitions (allowed status sequences per record type) cannot be exported as executable configuration. FlitStack AI exports the status transition matrix as a structured reference document so your Zoho admin can rebuild it as a Zoho Blueprint with matching stage gates. The reference document includes the complete transition matrix, required fields at each stage, and record-type gating logic.

FieldFX inventory location records (warehouse, truck stock, bin locations) migrate as a Zoho custom Locations module with fields for address, bin codes, and capacity. Stock level tracking requires Zoho Inventory to be licensed or a custom module with numeric fields to capture quantities. The migration creates the Locations module structure during the schema audit phase and populates it after Account and Contact migrations have committed.