Migrate from VisionFlow to Intercom

VisionFlow Issues map directly to Intercom Tickets. We preserve the unique VisionFlow ticket number in a custom attribute (vf_issue_number__a) for audit traceability, and the original creation timestamp migrates to the Ticket's created_at field. Status stages from VisionFlow map to Intercom Ticket status values (open, resolved, snoozed), and assignee mappings resolve against the migrated User records. Priority from VisionFlow migrates to the Ticket priority field. Cross-module Issue dependencies (Issues linked to Assets or Contracts) resolve through Intercom Custom Object lookups after the Assets and Contracts migration phase completes.

VisionFlow Customer records map to Intercom Contacts with full contact detail preservation. We map the customer name, email address, phone, and any custom fields configured in VisionFlow's CRM module to Intercom custom attributes. Organization linkages from VisionFlow (Customer belongs to Organization) map to the Intercom Contact-Company association, which we resolve during the Organizations-to-Companies migration phase before Contacts are imported. Customers without a matching Organization in VisionFlow create standalone Intercom Contacts with no Company association.

VisionFlow Organizations are top-level entities that group Customers, Assets, and Contracts under a company structure. These map to Intercom Companies. We import Organizations before Contacts so that the Contact-Company association is resolvable at Contact insert time. Organization hierarchy (parent-child relationships between organizations) maps to Intercom Company parent-account structure where the destination schema supports it, or flattens into a single Company record with a custom parent_org__a attribute if the hierarchy depth exceeds Intercom's flat model.

VisionFlow Asset records (inventory, hardware, software with lifecycle status tracking) have no native Intercom equivalent. We create an Asset Custom Object in Intercom with fields for asset name, lifecycle stage, location, custodian (linked to the Contact who is the asset's assigned user), and any custom fields VisionFlow has configured. Asset lifecycle stage (active, in repair, retired) migrates as a typed attribute. We flag any file attachments associated with Assets for separate extraction as ContentDocument records linked to the Custom Object.

VisionFlow Contract records with key dates, parties, and attached documents have no native Intercom equivalent. We create a Contract Custom Object in Intercom with fields for contract name, start date, end date, renewal type, and counterparty. Each Contract Custom Object is associated to the relevant Company record via a Company reference field. Document attachments migrate as ContentDocument records linked to the Contract Custom Object. Contract data that represents service-level agreements (SLAs) is flagged for manual recreation as SLA rules in Intercom's Help Desk settings.

VisionFlow Activities (work entries, time spent, and communications linked to Issues or Customers) map to Intercom Conversation Parts for activity timeline context. Activity type (call, email, meeting, note) determines the Conversation Part type, and the original activity timestamp preserves in the part's created_at field. Activity notes from VisionFlow migrate as internal Conversation Parts visible only to teammates. Large-volume activity histories use the Intercom REST API with batch chunking; we do not use Intercom's CSV import for activity records because parent record resolution requires API-level WhoId and WhatId linkage.

VisionFlow Ideas (internal tracking of suggestions and knowledge base contributions separate from Issues) map to an Intercom Custom Object named Idea with title, description, status, and author fields. If the destination team intends to use Intercom's Help Center for public-facing articles, we treat Ideas as source material for article drafts and deliver a written inventory of Ideas requiring review before publishing rather than auto-creating Help Center articles that may contain draft-quality content.

VisionFlow User accounts with roles and organizational membership governing access across modules map to Intercom Admins and Teammates. We extract all VisionFlow Users referenced on Issues, Activities, and Assets, match by email against Intercom User provisioning, and resolve owner references in the migrated records. Any VisionFlow User without a matching Intercom Admin account enters a reconciliation queue for the customer's Intercom admin to provision before the User-dependent record migration phase begins.

VisionFlow Workflows define multi-step process routing that Issues and other objects move through. These do not migrate as functional code because VisionFlow Workflows use a step-sequence and conditional routing model that has no equivalent in Intercom's workflow engine. We document every active VisionFlow Workflow during scoping — its trigger, steps, conditional logic, and SLA gates — and deliver a written inventory with recommended Intercom Inbox routing rules, SLA definitions, and resolution steps. The customer's Intercom admin rebuilds these as Rules and SLA policies post-migration.

VisionFlow Contracts that represent customer-facing SLA agreements (response time, resolution time, escalation paths) map to Intercom SLA Policies configured in Help Desk settings. We extract the SLA terms from VisionFlow Contract records, classify them by priority level, and deliver a configuration guide for the customer's Intercom admin to set up SLA Policies and assign them to the relevant Inboxes post-migration. SLA attachment documents migrate as ContentDocument records on the Contract Custom Object for reference.