Xdar

This game gives endless fun but it does carry some major glitches. They need to sort out first person view, period. Your view and where your actual bullets fire from are not in sync. In most FPS your view is linked with your weapon, in this game the bullets come from the gun, sounds realistic. It's not in practice.
Handrails and lots of other objects will stop your shots even when you have a clear view through your ironsights. They need a dedicated first person view model and camera, rather then zooming in to the third person model, this is why the world seems extra large.

That works for 360 distance, and if you use the same DPI for both games, the relation between the sensitivities stays the same. Matching 360 distance between games that have such different FOV's usually doesn't feel right tough. Especially converting CSGO hipfire 360 distance to PUBG scoping will feel way too sensitive. 

I was mistaken in my correction to the 8x/15x scope sensitivities before @DPI Wizard updated the calculator to have correct magnification values. So using my method, people should always have the same sensitivities for Scoped 2x/4x/8x/15x, regardless of their zoom sensitivity ratio. If you use zoom sensitivity ratio 1 in CS:GO, then it actually works out to where ALL of the sensitivities are in fact the same. This is because PUBG's sensitivities are scaled the same as CS:GO with zoom_sensitivity_ratio_mouse 1. If you are using any other value for zoom sensitivity ratio, then you will have a different value for Scoping, and then another different value that works for all of the Scoped 2x/4x/8x/15x sensitivities.
As an example, my (finally) correct personal sensitives now are:
Normal: 0.009900 VehicleDriver: 0.009900 Targeting: 0.009900 Scoping: 0.008749 Scope2X: 0.007731 Scope4X: 0.007731 Scope8X: 0.007731 Scope15X: 0.007731 So to be clear, all your sensitivities turn out to be the same in PUBG now that the calculator is corrected because you are using zoom sensitivity ratio 1 in CS:GO. In your case, that's 0.010890 across the board.
I will get around to amending the original post I made on my method to make it shorter and better organized, and also note the corrections that have been realized since then.

Updated and verified everything now (with the exception of 15x, I'm going by the datamined 12x on it).
A few notes:
I've updated the FOV to 80, which is most likely correct. The issue with measuring it is that the 1st person view is not actually 1st person. The camera is still slightly behind the pivot point. This is also true for the scopes! FOV for scoping is 70, and all scopes are based on this with their multipliers. If you set all the sensitivities to the same value, it is the same as 100% monitor match.