Significant discrepancy in Total Wordcount in WorldServer versus SDL Trados Studio 2017 when using the WorldServer 9x Scoping Mode

My project has been created in WorldServer using the WorldServer 9.x Scoping Mode as defined in the Project Type.
Once I export my project to a WSXZ Studio package and open the package in SDL Trados Studio 2017, the wordcount analysis in Studio differs significantly from the scoping report in WorldServer.

If the project was created using a Project Type, change the Scoping Mode defined in the Project Type to Studio scoping mode as displayed here:



It is also recommended to change the default Scoping mode in tm.properties file so the Studio scoping mode will be applied to Ad-Hoc projects as well. The default scoping mode is the one set in the tm.properties files on the server where WorldServer is installed. Open the tm.properties file and find this setting set per default:
 

#scoping_mode=worldserver9.x

Uncomment the property and set it to studio:
 

scoping_mode=studio

Save your change and restart WorldServer (Idiom Service).

If you are using Idiom Legacy Filters such as XML (NT) Filter, HTML (NT) Filter, PPT Filter, MIF Filter, JavaScript Filter, DOC Filter,  Excel Filter, note that these filters are no longer supported. Please change your WorldServer configuration to use Studio File Type filters to achieve a full integration with SDL Trados Studio.
 

The WorldServer project has been segmented using the WorldServer 9.x scoping mode. SDL Trados Studio applies the Studio Scoping Mode to analyze files.

Another reason for such a discrepancy is if you are using Idiom Legacy filters (no longer supported) instead of Studio File Type filters to segment your files.

There are a few CRQs for wordcount discrepancies for both WorldServer 11.4.3 and Studio as well as for 11.6.1 and Studio.

There are differences in the wordcount of WS 11.4.3 and 11.6.1 because of a bug fix made in WorldServer 11.6, CRQ-7622.

The wordcount in WS 11.6.1 has discrepancies with Studio.  A defect on the occurrence of this issue in WS 11.6.1, CRQ-22509.

Another cause of different and/or missing fuzzy matches from the Studio kit is by the settings of the user's preferences which controls the minimum score which is included in the Exported kit from Worldserver to Studio.
 

This article provides an example of how the 2 scoping modes lead to different results in SDL Trados Studio versus WorldServer:

Different TM leverages for same TM entry in exported WSXZ compared to WorldServer server TM