Migrate from VisionFlow to Salesforce Service Cloud

VisionFlow Issues map to Salesforce Case with ticket number preserved as Case.CaseNumber, status mapped to Case.Status, priority to Case.Priority, and assignee to Case.OwnerId via User lookup. We preserve the full status history as CaseHistory records. Any conversation threads attached to Issues migrate as EmailMessage records linked to the Case. On-premise deployments may require direct database extraction coordinated with VisionFlow support before Case creation begins.

VisionFlow Customer records map to Salesforce Contact. We preserve the customer name, email, phone, and address fields, and map the organizational association to a Salesforce Account via a pre-created Account record. Any custom fields configured on VisionFlow Customers are created as Salesforce custom fields on Contact before migration. Customer-Organization linkage in VisionFlow becomes the Contact.AccountId reference resolved at migration time.

VisionFlow Organizations (top-level entities grouping Customers, Assets, and Contracts) map to Salesforce Account. We use the Organization name as the Account Name and preserve any hierarchy information. Account is created before any Contact import so that the Contact.AccountId lookup is satisfied at the moment of Contact insert. If VisionFlow uses a parent-child organization structure, we replicate that as Account.ParentId in Salesforce.

VisionFlow Assets (inventory, hardware, software records with lifecycle status) map to Salesforce Asset. We preserve the asset name, serial number, status (Installed, Shipped, Retired, etc.), install date, and custodial relationship to the Account or Contact. If VisionFlow captures custom asset attributes (manufacturer, warranty end date, location), we create matching Salesforce custom fields on Asset during schema design.

VisionFlow Contract records map to Salesforce Contract. We preserve contract title, account association, start and end dates, status, and any attached documents as Salesforce Files. Contract key dates migrate to Contract.StartDate, Contract.ContractEndDate, and a custom reminder field. Signed or executed contract PDFs migrate as ContentDocument records linked via ContentDocumentLink to the Contract.

VisionFlow Activities logging work entries, time spent, and communications linked to Issues or Customers map to Salesforce Task (for work entries and logged time) and Event (for scheduled or completed meetings). We set ActivityDate to the original VisionFlow timestamp to preserve timeline ordering. The parent reference (Issue or Customer) becomes the Case or Contact lookup on the Task or Event.

VisionFlow Workflows define multi-step Issue processing with conditional routing. These are documented as a written inventory: we capture the workflow name, step sequence, conditions, and actions in a structured handoff document with a recommended Salesforce Flow Builder equivalent for each workflow. The customer's admin or a Salesforce partner rebuilds them post-migration. Migration scope does not include Flow construction.

VisionFlow Ideas (internal tracking of suggestions and innovative practices separate from Issues) map to Salesforce Idea if the destination org has the Ideas feature enabled. We preserve the idea title, description, author, and status. If Ideas are not available in the destination edition, we map Ideas to a custom object with matching fields.

VisionFlow User accounts with roles and organizational membership map to Salesforce User records. We resolve users by email match during migration. Any VisionFlow User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and team associations are documented for the admin to reassign in Salesforce profiles and permission sets.

File attachments linked to VisionFlow Issues, Customers, and Assets migrate to Salesforce ContentDocument linked via ContentDocumentLink to the parent Case, Contact, or Asset record. We extract files from the VisionFlow export package and upload them to Salesforce Files, preserving file names and content types. Large attachments (>25 MB per Salesforce limit) are flagged for chunking or alternative delivery.