Migrations impose challenges that are difficult to predict and these challenges may vary drastically from migration to migration. Furthermore, these challenges are magnified by software vendors, who do not instill confidence from the technical perspective.   Valiance addresses these challenges in a short and highly focused engagement to prove the suitability of our technology in our customer’s environment, the Proof of Concept (POC).

Valiance views the POC as a collaborative effort in conjunction with our customer, providing an opportunity to gain a solid understanding of TRUmigrate & TRUcompare product capabilities while enabling Valiance to acquire direct knowledge of the detailed requirements associated with the pending migration.   The scope of POC activity focus on risks identified for each specific customer and often includes:

1. Application compatibility—TRUmigrate & TRUcompare currently supports a broad variety of commercial off the shelf software.  The POC often verifies that Valiance’s products work with a specific application under the constraints of the source and target systems and performs as advertized in our customer’s environment.
2. Performance—testing performance is a function of data volume, network throughput and the volume of unstructured database elements, e.g., documents.  It is essential to test the actual throughput for planning purposes.  Note that TRUmigrate & TRUcompare products include features that enable multiple methods for remote migrations and support concurrent execution if these become necessary to enhance the product throughput. 
3. Configuration Efficiency—few would argue the value of configuration versus coding,  but what is the cost or labor associated with TRUmigrate & TRUcompare configuration?  The time required to configure TRUmigrate & TRUcompare should be compared to other migration approaches.  It is understood that this is often difficult to accurately predict; prior customer experiences for data migration should be a good starting point, i.e., what was the prior impact to the schedule and labor costs of traditional migration approaches?
4. Data Discovery (Pre-Migration Testing)—while certain data migration errors can only be discovered after completing the migration process and testing (unintentional special character substitutions for example) there are classes of errors that can be anticipated Data Discovery is often evaluated during a POC to verify applicability and value. 
5. TRUcompare 100% Verification Testing—post-migration testing is performed by transforming each source field value per the migration specification mapping and comparing this expected result with the actual result in the destination system.  The POC provides an opportunity to evaluate test scenarios to include representative transformation rules and actual testing will be conducted on-site.