Migrate from VisionFlow to Gorgias

VisionFlow Issues map to Gorgias Tickets with unique ticket numbers preserved as external_id for cross-reference. Status stages (Open, In Progress, Resolved, Closed) map to Gorgias Ticket status values, and priority fields map to Gorgias ticket priority (low, medium, high, urgent). Assignee resolution requires mapping VisionFlow Owner email to Gorgias agent user. Attachments linked to Issues migrate as file attachments on the corresponding Gorgias ticket. VisionFlow's multi-step Issue workflows are documented but not migrated as code; we deliver a written inventory for admin rebuild.

VisionFlow Customer records map 1:1 to Gorgias Customer profiles. Email address is the primary dedupe key and lookup anchor for ticket attribution. Phone, language, and timezone fields transfer to matching Gorgias Customer attributes. Any custom fields configured on VisionFlow Customers are created as custom fields in Gorgias (String, Boolean, Number, or Date types per Gorgias API specification). Organization linkages from VisionFlow are preserved as Gorgias Customer-Company associations.

VisionFlow Organizations (top-level entities grouping Customers, Assets, and Contracts) map to Gorgias Company records. Company name, domain, and address metadata transfer directly. VisionFlow's organization hierarchy — parent and child organizational structures — is flattened during migration: we create the primary Company record and attach all associated Customers, preserving the hierarchy description in a notes field. Gorgias Companies enable agents to view all open tickets for a customer organization in a single view.

VisionFlow Assets (hardware, inventory, software records with lifecycle status) have no native equivalent in Gorgias's ecommerce-focused data model. For teams where Asset records are support-relevant — equipment warranty tickets, hardware replacement requests — we migrate Assets as a Gorgias custom object with lifecycle stage, location, custodian, and asset tag fields created during schema setup. For teams where Assets are purely internal inventory unrelated to customer support, we flag them as out-of-scope and document the export for the customer's records.

VisionFlow Contract records (key dates, parties, attached documents) have no direct Gorgias equivalent. Contracts relevant to customer support — SLA agreements, service-level commitments tied to support entitlements — migrate as a custom object in Gorgias with contract dates, parties, and SLA terms fields. Contract PDF attachments migrate as file attachments on the custom object. We determine contract scope during discovery based on whether support entitlements are contract-driven.

VisionFlow Activities (work entries, time spent, communications linked to Issues or Customers) map to Gorgias ticket message records. Each Activity becomes a message on the corresponding Gorgias Ticket, with the activity type (email, call, note, internal note) mapped to the Gorgias message channel. Activity timestamps are preserved for chronological ticket history. We resolve the parent Issue reference to the migrated Gorgias ticket ID during the transform phase.

VisionFlow Ideas (internal tracking of suggestions and best-practice knowledge separate from Issues) can migrate as Gorgias Help Center articles if the customer's Help Center is active. We map Idea title, description, and author to a Gorgias article, preserving creation and update timestamps. Articles are published as draft by default for admin review before going live. This object is optional and scoped based on whether the Help Center migration is in scope.

VisionFlow Users (with roles and organizational membership governing module access) map to Gorgias Agents. We resolve VisionFlow User email to Gorgias agent email as the primary matching key. Role mapping is scoped during discovery: VisionFlow admin roles map to Gorgias admin, and support-agent roles map to Gorgias agent. Any VisionFlow User without a matching email in Gorgias is held in a reconciliation queue for the customer to provision before record import continues.

VisionFlow Workflows define multi-step Issue processes with conditional routing. We do not migrate Workflows as code because VisionFlow's step-sequence automation model has no direct Gorgias equivalent. Gorgias uses Rules (event-triggered) and Macros (agent-executed canned responses with field updates), which are a different architecture. We deliver a written inventory of every active VisionFlow Workflow: its trigger conditions, step sequence, conditional branches, and assigned actions, with a recommended Rules or Macros rebuild approach per workflow. The customer's admin rebuilds them post-migration.

VisionFlow tags applied to Issues, Customers, or Activities migrate to Gorgias Tags on the corresponding Ticket or Customer record. Tags are preserved as plain string labels and are available for filtering, reporting, and Rules conditions in Gorgias. We extract all distinct tag values during discovery and confirm coverage against the migrated records.

File attachments linked to VisionFlow Issues, Activities, Contracts, or Assets migrate as attachments on the corresponding Gorgias ticket or custom object. We extract files from the VisionFlow storage layer (cloud-hosted export or on-premise file store) and upload them to Gorgias via the attachments API. File naming conventions and upload order are preserved for agent reference. Attachment size limits follow Gorgias API constraints.

If VisionFlow's knowledge base module is active and contains customer-facing articles, we migrate them to Gorgias Help Center. Articles, categories, and structural hierarchy transfer to Gorgias's article and category structure. We preserve publication status (draft or published) and author attribution. This object is optional and requires confirmation during discovery that the KB module is in active use.