Getting issue while migrating from sharepoint 2010 with SQL server 2008 R2 to sharepoint 2013 with SQL server 2014.

See more:

SharePoint2013

Short Description:
The current production system has SharePoint 2010 with SQL Server 2008 R2 with customization. We need to migrate the SharePoint 2010 with SQL Server 2008 R2 to SharePoint 2013 with SQL Server 2014.
The Authentication method that is used in present SharePoint 2010 is Classic Mode. We need to migrate this from Classic mode to Claims mode since Classic mode is deprecated in SharePoint 2013.
The method that we are using is SharePoint Detach-Attach.
The custom code is build using .Net 3.5 framework and this needs to be upgraded to .Net 4.5 framework. Also upgrade the code to work in SharePoint 2013 (referencing all SP 2013 API’s and Locations)

Problem Statement:-
We have attached the Production SharePoint 2010 content database backup to development environment (DIT) which also contains SharePoint 2010 with SQL Server 2008 R2, mounted the database and cleaned up all the orphan features. Since we are not given permission to do clean-up on Production we have used this DIT as intermediate environment. We have taken the backup of content database from DIT and copied to a VM which contains SharePoint 2013 with SQL Server 2014 (SQL is configured in separate VM).
ü In the VM, we have created classic based web application (W1) in SharePoint 2013 and attached the SP2010 content database on the SQL Server 2014 and executed the Test-SPContentdatabase command against the W1 (web application). This throws basically 4 errors on missing features. We have cross verified all these 4 feature ID’s in the content database (SP2010) (all the Feature Tables) and we could not able to find any reference in the DB, also we have made sure that we have not installed those features (wsp) in the VM. But still from somewhere Test-SPContentdatabase is finding the reference of these 4 feature and throwing the error. We also tried deploying all the solutions in SP 2013 environment and followed same steps but still Test-SPContentdatabase is throwing the feature missing errors. With this errors in place if we run the Mount command, the upgrade fails. Need help in identifying the solution for this issue to run the upgrade successfully.

Log File:-

Category        : MissingFeature
Error           : True
UpgradeBlocking : False
Message         : Database [XXX_CDB] has reference(s) to a missing feature: Id = 
                  [3acf36a1-11c6-433a-8888-36e26d0db5ed], Name = [Autocomplete], Description = [SOAP based 
                  suggestion box for Text Fields.], Install Location = 
                  [XXX.FFFFFF.XXX.Autocomplete_Autocomplete].
Remedy          : The feature with Id 3acf36a1-11c6-433a-8888-36e26d0db5ed is referenced in the database 
                  [XXX_CDB], but is not installed on the current farm. The missing 
                  feature may cause upgrade to fail. Please install any solution which contains the feature 
                  and restart upgrade if necessary.
Locations       : 

Category        : MissingFeature
Error           : True
UpgradeBlocking : False
Message         : Database [XXX_CDB] has reference(s) to a missing feature: Id = 
                  [729c87c0-67b9-497f-ac4f-8393d8510970], Name = [XXX.FFFFF.XXX.Indexation - 
                  Indexation Data Upload - Site], Description = [This feature is to define indexation data 
                  upload document library template.], Install Location = 
                  [XXX.FFFF.XXX.Indexation_IndexationDataUploadSite].
Remedy          : The feature with Id 729c87c0-67b9-497f-ac4f-8393d8510970 is referenced in the database 
                  [XXX_CDB], but is not installed on the current farm. The missing 
                  feature may cause upgrade to fail. Please install any solution which contains the feature 
                  and restart upgrade if necessary.
Locations       : 

Category        : MissingFeature
Error           : True
UpgradeBlocking : False
Message         : Database [XXX_CDB] has reference(s) to a missing feature: Id = 
                  [28401a0d-1024-42d8-a72c-b4fef53a5d46], Name = [XXX.SharePoint.ABS - ABS Report - Site], 
                  Description = [This feature is to set up the RBA XXX report library/template definition.], 
                  Install Location = [SSS.SharePoint.XXX_XXXReportSite].
Remedy          : The feature with Id 28401a0d-1024-42d8-a72c-b4fef53a5d46 is referenced in the database 
                  [XXX_CDB], but is not installed on the current farm. The missing 
                  feature may cause upgrade to fail. Please install any solution which contains the feature 
                  and restart upgrade if necessary.
Locations       : 

Category        : MissingFeature
Error           : True
UpgradeBlocking : False
Message         : Database [XXX_CDB] has reference(s) to a missing feature: Id = 
                  [e29f4991-f6d9-47db-b2a9-d084f2fd6a84], Name = [RBA Reporting - Site], Description = [This 
                  feature is to set up the RBA report library/template definition.], Install Location = 
                  [TSS_SharePoint_RBAReportingSite].
Remedy          : The feature with Id e29f4991-f6d9-47db-b2a9-d084f2fd6a84 is referenced in the database 
                  [XXX_CDB], but is not installed on the current farm. The missing 
                  feature may cause upgrade to fail. Please install any solution which contains the feature 
                  and restart upgrade if necessary.

What I have tried:

while migration facing above issue.