Migrate from Vtiger All-In-One CRM to Microsoft Dynamics 365 Sales

Vtiger Accounts map directly to Microsoft Dynamics 365 Sales Account. The Account Name, Website, Industry, and Address fields migrate as typed fields. We use Account Name as the dedupe key during import and validate that the Billing Address and Shipping Address are correctly separated in the Dynamics 365 schema, as Vtiger conflates address fields under a single address block. Custom fields on Accounts migrate to Dynamics 365 custom attributes.

Vtiger Contacts map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (First Name, Last Name, Email, Phone, Mobile) migrate cleanly. We preserve the Contact-to-Account relationship by resolving the parent Account record before Contact insert. Custom fields on Contacts migrate to Dynamics 365 custom attributes with field-type mapping from Vtiger picklist, checkbox, date, and currency types to equivalent Dynamics attribute types.

Vtiger Leads map to Dynamics 365 Lead with Lead_Status, Lead_Source, and Industry fields explicitly mapped to their Dynamics 365 equivalents. The conversion readiness of Vtiger Leads (qualified versus unqualified) is preserved through the leadsourcecode and statecode attributes. We flag any Vtiger Leads that were in an active conversion workflow at export time so the customer can complete conversion manually post-migration.

Vtiger Potentials map to Dynamics 365 Opportunity. The Potential Name becomes the Opportunity Name, Amount maps to Est. Revenue, and Close Date maps to Close Date. The Sales Stage in Vtiger maps to a Microsoft Dynamics 365 Sales Process stage; we configure the Sales Process and stage values during schema setup before migration begins. Multi-currency Potentials require the Dynamics 365 Currency field to be set per record, which we resolve from the Vtiger currency_id lookup.

Vtiger Help Desk Tickets map to Dynamics 365 Customer Service Hub Case. Ticket Status, Priority, and Assigned Agent migrate to Case Status, Priority, and Owner respectively. Vtiger ticket categories and internal notes migrate to Case Title, Description, and internal Case Comments. If the customer used Vtiger's social ticketing or round-robin assignment rules, we flag these for manual rebuild in Dynamics 365 Customer Service as they are configuration data rather than records.

Vtiger Products migrate to Dynamics 365 Product. We handle the Product-Category relationship by mapping Vtiger Product Categories to Dynamics 365 Product Families or custom categories. Unit of Measure from Vtiger migrates to the Dynamics 365 UoS Name and UoS Schedule. Vtiger's product-level pricing and stock information (when the Inventory module is enabled) migrate to the Dynamics 365 Product entity with Price and Stock Level fields.

Vtiger Quotes map to Microsoft Dynamics 365 Sales Quote. We audit the Inventory module status before extracting Quote data; if Inventory is disabled, Quotes are unavailable and we flag this in the pre-migration scope report with a recommendation to enable Inventory before re-running the export. Quote line items migrate to Quote Details with Product lookup resolution from the Product import phase. Quote status (Draft, Delivered, Accepted, Lost) maps to the Dynamics 365 statecode.

Vtiger Sales Orders map to Microsoft Dynamics 365 Sales Order. Line items migrate with Quantity, Unit Price, and Tax fields preserved. Products must exist in Dynamics 365 before Sales Orders are imported to satisfy the referential integrity requirement. We sequence Sales Orders after Products in the import order. Any Vtiger Sales Order linked to a missing Product is flagged in a reconciliation report for the customer to resolve before proceeding.

Vtiger Projects migrate to Dynamics 365 Project Operations or Project for the Web depending on the destination licensing. Task-level dependencies (Finish-to-Start) are preserved as Task Dependencies in Dynamics 365 Project. Milestones migrate as Project Milestones. If the destination does not include Project Operations, we flatten Projects to Tasks attached to the parent Account and flag this in the pre-migration report.

Vtiger attachments export as individual files per parent record with no bulk download option. We stage files in object storage and re-associate them with their parent records post-import using Dynamics 365 SharePoint or OneDrive integration. For migrations with more than 500 attachments, we add a dedicated staging phase to the timeline. Customers must provision adequate SharePoint or OneDrive storage in the destination tenant before migration.