If OneDrive is being provisioned by IT for all users, then you probably won’t need a Drive Mapping, they will all be in %USERPROFILE% with folder names specified by IT. I have 3 x OneDrive folders:

• “<CompanyName>” is the equivalent of our old shared network drive
• “OneDrive-<CompanyName>” is my personal folder on the Company OneDrive Account. I used to have a drive mapping to a user folder on the server, this replaces that mapping.
• “OneDrive” is my personal account set up by me.

OneDrive is very nice piece of kit, but when it is replacing a busy server it can become a bit of a lumbering beast and take a while to update. It is good but its NOT a direct replacement for a proper File Server, make sure you only use it when you need to. Don’t use it for Temp files (use %TEMP%), don’t use it for User Settings/Files (have a folder in %AppData%). I would totally avoid using it for any multi user data that has timing consequences or locking of any kind (e.g. SqlLite or monitored file drop folders). There might be a few programming techniques you want to avoid when using OneDrive. E.g. creating a big CSV using Append Mode, then immediately renaming might cause it have a bit of a fit. Rapid changes are best done in a Temp folder then copied to OneDrive in 1 go.

If you don’t have so much control over the Folder Names or there is a varying hierarchy, then you might still need a Mapped Drive (to the correct local folder). This might be a good migration path, just change your existing Network Drive Mappings to Local Drive Mappings in the OneDrive structure, but it might equally be a good chance to move from Drive Mappings and use %USERPROFILE% as your UNC Root.