Migrate from Vtiger Sales to Salesforce Sales Cloud

Vtiger Leads map directly to Salesforce Lead. Lead status values migrate to Salesforce Lead Status with any custom status field preserved as a custom field. Lead source and rating (Hot, Warm, Cold) translate to Salesforce LeadSource and Rating. Owner assignment resolves via email match to the destination Salesforce User table.

Vtiger Contacts map to Salesforce Contact, but Salesforce requires an AccountId on every Contact. We create all Accounts from Vtiger Organizations before inserting Contacts, then populate AccountId on each Contact during import using the Organization-Account link preserved in Vtiger's accountid field. Any Contact without a resolved AccountId is held in a reconciliation queue for admin review before the next migration phase.

Vtiger Organization records map 1:1 to Salesforce Account. Industry, annual revenue, phone, website, and billing address migrate directly. The Organization name becomes Account Name. Account is inserted before any Contact import to satisfy the foreign-key dependency. We use Industry and Type from Vtiger to populate corresponding Salesforce picklists, flagging any unmapped values for admin review.

Vtiger Deals map to Salesforce Opportunity with Amount, CloseDate, Stage, Probability, and Description preserved. The Deal's related Organization becomes the Opportunity AccountId; the related Contact becomes the Opportunity ContactId via OpportunityContactRole. Vtiger's sales pipeline assignment maps to a Salesforce Sales Process and Record Type that we configure before migration. Closed-Lost and Closed-Won dates from Vtiger become Salesforce CloseDate with the appropriate StageName.

Vtiger Quotes migrate to Salesforce Quote, which is available on Sales Cloud Professional and above. Quote line items map to QuoteLineItem with Product2 and Pricebook2 references resolved at migration time. Quote PDFs and attachments migrate as ContentDocument records linked to the Quote via ContentDocumentLink. Vtiger Quote status (Created, Delivered, Approved, Accepted) maps to Salesforce QuoteStatus.

Vtiger Sales Orders map to Salesforce Order, which requires the Order Management feature to be active in the destination org. Sales Order line items migrate to OrderProduct with Pricebook2, Product2, Quantity, and UnitPrice resolved before insert. The related Contact and Account references transfer from Vtiger's quote relationship. If the destination org does not have Order Management enabled, we map Sales Orders to OpportunityLineItem records and flag the configuration gap for the customer before migration begins.

Vtiger Invoices do not have a native Salesforce equivalent outside of Salesforce Billing (a separate product). For most migrations we map Invoices to OpportunityLineItem records with invoice number and payment status preserved as custom fields. If the customer has Salesforce Billing or Financial Services Cloud, we create Invoice records with the correct line-item structure. Invoice payment status, due date, and PO reference migrate as custom fields.

Vtiger Help Desk Tickets map to Salesforce Case. Ticket status (Open, Wait, Closed) maps to Case Status with custom status values preserved. Priority and category migrate to Case Priority and a custom category field. Conversation history including customer replies and agent replies migrate as EmailMessage records threaded to the Case, preserving timestamp and author. Assigned agent resolves via email match to Salesforce User. Vtiger ticket pipelines map to Case Record Types if multiple support queues exist on the source.

Vtiger Projects do not have a direct Salesforce standard object. We create a Salesforce custom object named Project__c with fields for project name, status, start date, end date, milestone count, and assigned user. Milestones and subtasks migrate as related Project_Milestone__c and Project_Task__c custom objects with parent-lookup relationships. Kanban and list view configuration is not stored as data and does not migrate.

Vtiger Products map to Salesforce Product2 records with the product code, description, unit price, and vendor name preserved. The Vtiger product category becomes the Salesforce Family picklist value. We create Standard Price Book entries for each product during migration so that PricebookEntry records exist before any Opportunity line items are loaded.

Vtiger Price Books store product-to-price mappings that differ structurally from Salesforce's PricebookEntry model. We unroll each Vtiger Price Book entry into Salesforce PricebookEntry records tied to the Standard Price Book or a custom Price Book, preserving the currency, price, and minimum quantity. Multi-currency Price Books require the destination Salesforce org to have Multi-Currency enabled before migration.

Vtiger Users migrate as a lookup reference table rather than inserted records because Salesforce User provisioning is an admin-controlled action. We extract every distinct user from Vtiger's Contacts, Deals, Tickets, and Projects, map them by email address to existing Salesforce Users, and flag any user with no Salesforce match as an orphaned owner requiring manual provisioning before migration of the records they own can proceed.

Vtiger custom fields on any standard module migrate to Salesforce custom fields of equivalent data type. Text fields map to Text, picklists to Picklist or Global Value Set, date fields to Date, numeric fields to Number or Currency depending on the Vtiger field type. We pre-create all custom fields in the destination Salesforce org before any data import so that field IDs are available during record insert. Custom field API names follow Salesforce __c convention matched to the Vtiger field name.

Vtiger attachments are stored as file references on Contacts, Organizations, Deals, and Tickets. We extract attachment metadata (filename, size, mime type, record association) and migrate them as Salesforce ContentVersion records. ContentDocumentLink records are created to attach each file to the corresponding parent record in Salesforce. Actual file transfer depends on Vtiger's hosting configuration and access controls; we assess this during the pre-migration audit and flag any file that cannot be accessed programmatically.

Vtiger tags apply across modules to label records. We extract all tag assignments per record and migrate them to Salesforce either as a multi-select picklist field on the relevant object or as Salesforce Topics with TopicAssignment records. The customer chooses the tagging strategy during scoping, as the choice affects reporting and filtering in the destination org.