Home  >   Articles   >  Migration Timeframe and Process

Migration Timeframe and Process

Bindu Rekha Babu
21 Sep, 2020 - Updated 1 year ago
Table of Contents


It’s easy to import CSV records and other data into Vtiger using built-in data import tools. However, if you have complex CRM configurations and data structures and want help migrating to a Vtiger Cloud edition, then let us deliver a turnkey solution in 1 to 4 weeks by purchasing one of our migration packages.

Open Source to On-Demand

The number of days required to complete the migration ranges within 2-3 days, successfully.

Following factors influence the migration time span:

  1. Size of database
  2. The data present in the database — Missing tables, corrupted tables, misplaced values, and columns should be organized
  3. Custom information present in the database


  1. After the migration, your Vtiger OnDemand data will be replaced entirely by the Open Source data.
  2. Currently merging of two CRM accounts is not possible in Vtiger.

Other CRM to Vtiger Cloud CRM Migration

We offer migration from the below CRMs to Vtiger cloud migration for free:

  1. Salesforce
  2. Sugar
  3. ACT
  4. MS Dynamics
  5. Goldmine
  6. ZOHO
  7. Suite


1. Backup files.
2. Attachments / Documents
3. Vtiger cloud account details ( Username/ instance URL )
4. Grant Vtiger ondemand support access in cloud account

The migration is done in a three-phased manner

Phase 1: Evaluation of backup files.

The migration team will verify if the files sent to us are correct.
The migration team will verify and update what data will be migrated and unsupported modules, which cause hurdle to start the migration.
This process of evaluation will take 2-3 business days. After evaluation, we will provide the estimate to complete a dry run.

Phase 2: Test run

We will map the data with Vtiger modules and migrate the data to the cloud account.
After completing, we will notify the customer to review the migrated data and report if any issues are noticed. The customer needs to review and share feedback within three business days. We will set up the test run within 2-4 weeks.
Opportunity owners should make sure they get the response within 2-3 business days.
In this phase, the customer should continue using their source CRM.

Phase 3: Final migration

After the customer reviews and approves that the migrated data is correct then the final migration process starts
The customer has to share the latest database backup for the final migration, and stop using their source CRM. Cloud accounts should also not be used during this phase.
The final migration will be done within 1 or 2 business days
We do offer migration on weekends at an additional cost of $250 (If the customer doesn’t want any downtime)
Weekend migration requests should be updated to the migration team one week ahead

The elapsed time limit to complete the migration ranges within 2-3 weeks.

Following factors influence the migration time span:

  1. Size of database
  2. Number of custom fields
  3. Relations
  4. Picklist values

What we migrate

  • Module’s data
    • Accounts
    • Contacts
    • Leads
    • Opportunities
    • Campaigns
    • Products
    • Tickets
    • FAQs
    • Services
    • Service Contracts
    • Assets
    • Vendors
    • Pricebooks
    • Calendar (Tasks)
    • Events
    • Projects
  • Custom fields
  • Custom Picklist Values
  • Fields Mapping
  • Documents and Attachments (Based on the input data)
  • Emails and Comments

What we don’t migrate

  • Extension’s data
  • Custom modules (Not supported by Vtiger)
  • Custom changes (Either code level or database level)
  • Module Layout design (Ex: Fields ordering, blocks creation, etc.)
  • Reference fields (Related fields that are not supported by Vtiger)
  • Merging of two instances
  • Removing duplicates
  • Roles and Profiles
  • User’s login history and records history
  • Workflows, reports, and settings


  1. ETA may vary based on the records count and custom fields.
  2. Currently, we are not migrating documents and attachments for MS Dynamic CRM.
  3. After the migration, your Vtiger OnDemand data will be replaced entirely by the migrated data.
  4. Currently merging of two CRM accounts is not possible in Vtiger.
  5. Once Migration is started, you should not use the Open Source Version and begin using the Vtiger OnDemand version.
  6. Modifications, configurations, workflows and other data will be lost when a second migration from the Open Source is done on Vtiger On-Demand, and all the configurations need to be done again.

Was this article helpful?
1  out of  1  found this helpful.
Comments 0
Be the first to comment
© Copyright 2022 Vtiger. All rights reserved.