Migrate from VisionFlow to Zoho Desk

VisionFlow Issues map to Zoho Desk Tickets. We extract ticket number, subject, description, status, priority, assignee, created date, modified date, and any custom fields configured on the Issue object. VisionFlow status stages map to Zoho Desk Ticket Status values (Open, Pending, On-Hold, Resolved, Closed). Priority maps to Zoho Desk Priority (Low, Medium, High, Urgent). Attachments are extracted from VisionFlow separately and re-linked in Zoho Desk as threaded Comments on the Ticket. We validate required Zoho Desk fields (Subject, Department) against the CSV format before submission to Zwitch.

VisionFlow Issue comment threads and internal notes map to Zoho Desk Ticket Threads (the chronological conversation view) and Ticket Comments. Each comment maps to a thread entry with author, timestamp, and content. VisionFlow internal notes are distinguished from customer-facing comments using the isInternal flag in the Zoho Desk CSV schema. We preserve the full comment chronology so that agent context from VisionFlow carries forward into Zoho Desk's ticket timeline.

VisionFlow Customer records (person-type contacts with names, emails, phone numbers, and organizational associations) map to Zoho Desk Contacts. We resolve the AccountId reference by matching the VisionFlow customer's linked Organization to a Zoho Desk Account. Custom fields on VisionFlow Customers migrate as Zoho Desk Contact custom fields scoped to the department receiving the data. Email addresses serve as the dedupe key during Contact import.

VisionFlow Organizations (top-level company entities that group Customers, Assets, and Contracts) map to Zoho Desk Accounts. The organization name becomes Account Name, industry and website map where present, and hierarchy (parent-child organization structures) maps to the Account.ParentId relationship in Zoho Desk. We resolve the parent Organization reference before importing child Contacts so that AccountId is populated on every Contact record.

VisionFlow Assets (inventory, hardware, and software records with lifecycle status and custodian assignment) map to Zoho Desk Products. Lifecycle stage, location, and custodian fields become Zoho Desk Product custom fields. Asset serial numbers map to the Product2 ProductCode field for inventory tracking. If the organization uses Zoho Desk's asset tracking features, we coordinate on the appropriate destination module during scoping — Products is the standard mapping; dedicated asset management may route to Zoho Inventory or a separate Products module configuration.

VisionFlow Contract records with key dates, parties, and attached documents map to Zoho Desk Contracts. Contract title, description, start date, end date, and associated AccountId (linked through the VisionFlow contract's organization reference) migrate directly. File attachments require separate extraction from VisionFlow and manual re-upload to Zoho Desk because Zoho Desk's assisted migration does not migrate attachments for Contracts module records. We flag attachment inventory during scoping and include a file inventory in the handoff package.

VisionFlow Activity records (work log entries, time spent, and communications linked to Issues or Customers) map to Zoho Desk Tasks. Activity type, description, duration, and timestamp migrate to Task fields (Subject, Description, ActivityDate, TimeSpent). Activities linked to specific VisionFlow Issues resolve to the migrated Zoho Desk Ticket ID. Activities linked to VisionFlow Customers resolve to the migrated Zoho Desk Contact. We do not map Activities to Zoho Desk's native Time Entries module unless the destination subscription includes the Contracts add-on for time tracking.

VisionFlow Ideas (internal suggestions and best-practice knowledge entries separate from Issues) map to Zoho Desk Knowledge Base articles. Idea title becomes the article Title, description becomes the article Body, and any categorization metadata becomes Knowledge Base category assignments. We do not migrate Ideas as configured Knowledge Base articles because VisionFlow's knowledge model is separate from its Issue tracking and Zoho Desk's KB structure requires department-specific article creation. The Ideas content is delivered as structured CSV with the Zoho Desk KB article template so the customer's admin can publish efficiently.

VisionFlow User accounts with roles and organizational membership map to Zoho Desk Agents. We match by email address to resolve the Zoho Desk Agent record. VisionFlow role schema varies by deployment and requires field-level review during scoping — roles map to Zoho Desk permission profiles (Support Administrator, Support Agent, Light Agent) and department assignments. Users without an email match in the destination Zoho Desk portal are held in a reconciliation queue for the customer's admin to provision before record import proceeds.

VisionFlow Workflows define multi-step processes that Issues and other objects move through. We document each workflow's trigger conditions, step sequence, conditional routing, and actions during scoping. Zoho Desk Workflow Rules (available from Professional tier) use a different model: record-triggered rules, time-based actions, and custom Deluge functions rather than a visual step builder. We deliver a written Workflow inventory with trigger-event mapping and recommended Zoho Desk Blueprint equivalents. Workflows are not migrated as code. The customer's admin rebuilds them in Zoho Desk after go-live.

VisionFlow Contract key dates (start, end, renewal) do not automatically trigger SLAs in Zoho Desk. We document the SLA conditions tied to VisionFlow contract tiers (if contract type influences response time or resolution time commitments) and recommend Zoho Desk SLA Policies configured per department or ticket category. SLA configuration is outside standard migration scope and is included as a written recommendation in the handoff package.

VisionFlow preserves full status history on Issues with timestamp and actor. We extract the status change log as a separate table and attach it to the corresponding Zoho Desk Ticket as a threaded comment or as a custom field group. Zoho Desk does not natively store a structured status history timeline, so we use a convention of internal comments prefixed with '[Status History]' that preserves the before/after status, the actor, and the timestamp for audit compliance.