Spotify (developer team, R&D, community outreach etc.) and community (for backing, obviously),
Looking at all the posts and comments about Facebook accounts--as well as being one of those... *ahem* paying... people myself who wants to disassociate from FB, without going through the drawn-out process of closing my account, getting everything transferred over and then having to reinstate my wife and daughter's premiums too--I thought I'd put a little piece together in the hope that someone from the great Spotif-eye-in-the-sky team sees it and reacts in a way that benefits the users.
With Spotify being the size that it is, it can safely be assumed that our account info, usernames, encrypted passwords, names, DoBs etc. are held in a database, which undoubtedly contains various tables and subsequent columns, and fields, and the inevitable data, regardless of where it comes from.
Knowing how DBs work, and considering how many users in the WORLD are actually paying for the service, how hard can it be to get just a single analyst--not even a developer just yet--to look into the differences, in terms of table-data, between a FB account and an email account? Once these differences are identified, the analyst could pass that data over to a developer who could then work on a conversion procedure that would strip any requested account of its link to FB and either leave it where it is but as an email account or create a new copy of the original but still, as as email account, with no implications (losses) to the user.
My guess--it is totally a guess as I really don't know anyone in the Spotif-identify-and-develop team for access to insider information--is that there would be a table for "Facebook created accounts" and one for "Email created accounts". With these there would be a join (maybe even a copy of the basic FB-account info in the email account table) so that one type of user can log in using the same screen as another type of user; however, it's safe to assume that both types of account have data that stand side-by-side, so in summary, I can only assume that it would be a straight-forward compare and convert from one to the other; the email address is already there in the base data... how do you think we get emails?!
I understand that as users, we don't pay for a subscription; we pay for a service that we want, not need--like a window cleaner--and that all the money from us goes into artists' payments, employees' wages, stuff like that, but you can't expect us to think you can't spare a few hours' worth of wages for a small number of people to sit and design a resolution for people who are providing their wages, can you?
I also understand that in this case, you hold the cards... and no matter how much we shout "I'm paying, I shouldn't have to do this!", we must accept that if we don't like, we must go elsewhere... but please, listen up and consider the kudos you'd get; imagine the badges 😉
Cheers for reading, hopefully something comes from this.
PS. I'd even be happy to look at a sample of dummy data myself and give suggestions, free of charge! I bet there'd be others willing to join me/collaborate too!
Updated on 2017-07-20
Hi and thanks for your well thought out contribution! A similar idea has also been suggested here:
https://community.spotify.com/t5/Live-Ideas/Implement-a-way-to-transfer-from-a-Spotify-account-created-using/idi-p/331226
Add your likes and comments (perhaps this post as a comment) there please!