Migrate from Vtiger Sales to Microsoft Dynamics 365 Sales

Vtiger Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (name, email, phone, address, title) migrate 1:1. Custom Contact fields migrate to Dynamics custom fields created in the pre-migration schema phase. The Contact's linked Organization becomes the Contact's accountid reference to the Account record created from the same Vtiger Organization. Owner assignment migrates by email matching to Dynamics User records; unresolved owners go to a reconciliation queue.

Vtiger Organization maps to Microsoft Dynamics 365 Sales Account. Organization fields (company name, website, industry, address) migrate 1:1 to Account. The Organization's domain or website becomes the Account deduplication key during import. Account must be created before Contact import so that accountid references are satisfied at insert time. Vtiger Organization custom fields map to Account custom fields.

Vtiger Lead records map directly to Microsoft Dynamics 365 Sales Lead. Lead source, status, and rating migrate to corresponding Dynamics Lead fields. We preserve any Vtiger lead scoring values in a custom field vtiger_lead_score__c on the Dynamics Lead. The customer's admin can run the Lead-to-Account-Contact Convert action post-migration once all records are in place.

Vtiger Deal (Potentials) maps to Microsoft Dynamics 365 Sales Opportunity. Deal stage maps to Opportunity StageName; we configure a Sales Process and Record Type in Dynamics before migration to match the Vtiger pipeline stages. Deal amount, probability, expected close date, and sales pipeline assignment migrate directly. Deals linked to Organizations or Contacts carry the resolved accountid and contactid references.

Vtiger pipeline stages map to Dynamics Opportunity Stage values via a pre-migration stage mapping document. We configure the corresponding Sales Process in Dynamics so that each Vtiger stage appears in the correct dropdown and probability is set per the customer's pipeline configuration. If the customer uses multiple Vtiger pipelines, each becomes a separate Record Type on Opportunity.

Vtiger Quote records linked to Deals migrate to Microsoft Dynamics 365 Sales Quote. Quote line items map to QuoteLineItem records; we resolve the Pricebook2 reference during import. Quote PDFs and attachments migrate as SharePoint document references or as ContentDocument records linked via ContentDocumentLink to the Quote. Quote status (Draft, Active, Accepted, Revised) migrates directly.

Vtiger Sales Order records map to Microsoft Dynamics 365 Sales Order. Line items, quantities, prices, and billing/shipping addresses migrate to Order Product records. PO reference and order status transfer to corresponding Dynamics Order fields. If the destination Dynamics org has Finance and Operations or Business Central, Order can integrate natively; standalone Sales uses Order for post-quote fulfillment tracking.

Vtiger Invoice records migrate to Microsoft Dynamics 365 Sales Invoice. Invoice line items, payment status, due dates, and related Contact and Organization references transfer. Payment status (Paid, Unpaid, Overdue) maps to Dynamics Invoice status. We flag Invoice records as historical if the original Vtiger status was Closed, as Dynamics Invoice is typically used for active billing tracking.

Vtiger Help Desk Ticket records migrate to Microsoft Dynamics 365 Sales Case if the destination org includes Service Cloud or the Case object is active. Ticket status, priority, category, and assigned agent map to Case Status, Priority, Category, and OwnerId respectively. Customer and agent reply threads migrate as EmailMessage records linked to the Case. Vtiger ticket pipeline becomes Case Record Type with stage-to-status mapping.

Vtiger custom fields on any standard module migrate to Dynamics 365 custom fields created in the pre-migration schema phase. We extract field name, data type, and picklist values from Vtiger and map to the nearest equivalent Dynamics field type (text, number, picklist, boolean, datetime). Custom field definitions are created in a Sandbox org first and validated before production migration. Vtiger field-level access control settings (gated to paid tiers) do not migrate and must be reconfigured in Dynamics security roles post-migration.

Vtiger User records (name, email, role, profile) extract for migration scoping. Owner assignments on Contact, Organization, Deal, Quote, and Ticket records are remapped to Dynamics User records by email matching. Any Vtiger Owner without a matching Dynamics User is held in a reconciliation queue; the customer's Dynamics admin provisions missing Users before record import resumes.

Vtiger Price Books are pricing list objects with product-to-price mappings that must be unrolled into Dynamics Product2 records and PricebookEntry records. Each Price Book entry in Vtiger (product reference + price) becomes a Product2 with a corresponding Standard Pricebook entry. Customers using multiple Price Books in Vtiger receive multiple Pricebook2 records in Dynamics, each with its own PricebookEntry set.