Hi @nhutwelker,
Are you looking at odrive as a migration tool instead of a user front-end to storage? I am still not quite clear where odrive fits in this scenario.
It sounds like you want to move to Google Cloud storage while keeping your existing Windows (SMB?) network shares mounted and available to your users, is that correct? There isn’t really a way to use odrive via a network mount type of interface, like typical Windows network shares, with drive letter mappings.
However, you can use odrive to interface to local server storage via WebDAV, FTP, or SFTP. If there was a WebDAV interface on top of your local server storage, for example, you can link that with odrive. You can find some information about that here: How do I setup a WebDAV Server on Windows and link it to odrive?
You could, of course, use odrive to interface to the Google Cloud Storage buckets (during and after migration is taking place), giving your users a Windows Explorer-based interface, although placeholders will be a new concept. You can use Google Cloud IAM roles/policies to manage user access to the bucket(s), making them read-only, if you wish.
I may still not be getting the full picture here, so please let me know if I am missing the point here.