There is a program to convert Sonar files to Reaper, so I imagine there could be one (if not now, soon) for S1-3.

urgh thank you Kylotan
 

I edited my post above, but the forum has completely deleted it instead. So here it is again:
 
I moved over to Studio One a year or so ago, and with recent events, I feel I'm one of the lucky ones.
 
Sadly there is no explicit migration process, so it's hard work. Here's what worked well enough for me, on the songs I needed to move over:

1. Take screenshots of Track and/or Console view to make sure you know which tracks and instruments you need to re-create in the destination project, what tempo you want, etc. If you're doing this for a lot of songs, you probably want to spend an hour or so in Studio One making a big song template with all the tracks and instruments you are likely to want, so you don't have to do this manually each time. It's easier to delete unwanted tracks after using a comprehensive template than it is to have to add them over and over again for each song.
2. Use the preset capabilities built in to individual plugins to ensure that your settings are saved outside of all the DAWs, and then you can load that custom preset in the effect or instrument once it's inserted into Studio One.
3. S1 doesn't have track templates but it does have FX Chains, so if you have tracks or track templates with a lot of FX involved, consider making and saving FX Chains to speed up the process of setting up these tracks. If you created new per-effect presets as mentioned above this can go pretty quickly.
4. MIDI clips can be dragged from Sonar to the Windows Desktop and then dragged right into an instrument track in Studio One. Save time on projects with lots of clips by combining all the clips in a track before doing this.
5. Audio clips can be exported via File > Export > Audio. Make sure you do Select All beforehand, or explicitly select the region you care about. Choose 'Tracks' in the export dialog, and make sure your Mix Enables checkboxes do what you want. If you're confident you can recreate the FX chain in Studio 1, you can clear Track FX. If you're not confident, perhaps because you use Sonar-specific stuff like Pro Channel, you might want to leave it selected and print the effects into the exported audio. (While you're there, consider exporting buses and/or the entire mix too, if you can spare the disk space.) Again, audio files can be dragged into an audio track in Studio One. (It will usually prompt you to copy them into the song's media directory later. DO NOT DELETE THE TRACKS EXPORTED FROM SONAR UNTIL YOU ARE 100% CONFIDENT THAT STUDIO ONE HAS A NEW COPY UNDER THE SONG DIRECTORY. USE THE MENU OPTION SONG>COPY EXTERNAL FILES IF NECESSARY.) You're almost certainly going to need to bounce down any Region FX or Clip FX, but the latter at least can be re-applied quite easily in S1.

Another helpful thing to know is that you can usually have S1 and Sonar running at the same time, which makes it easier to compare the layouts, and even the tone upon playback. You may need to switch driver models from ASIO to something else, at least in one of the DAWs.

Thanks that's very helpful I was intending to create a version of my SPLAT template on Studio One 1st so looks like that's the way to go. Also if you use Console 1 you'll definitely need to have both DAW's running at same time so you can copy any settings you've changed although I'll check with Softube if there is any way to save them outside DAW.

Kylotan
 
Sadly there is no explicit migration process, so it's hard work. Here's what worked well enough for me, on the songs I needed to move over:
 

Great post! Thanks, man, for your diligence on this. It will make a big difference for me.

Yeah, wouldn't it be sweet to have THAT routine written by someone!  In my case, I have 15 years and around 1600 songs that are all in Cakewalk format.  So I'll NO choice but to maintain a computer with a copy of Cakewalk on it down the road.  It would be especially awesome for a routine to open Cakewalk Bundles! Man!  Would THAT save a lot of us some grief down the line!

Just keep using sonar as it will continue to work. Not sure why the panic.  I still have some software tools that have been running on Windows 8 that started back on Win 95.    If people are that concerned over the future and afraid it will suddenly break (Sonar 8.5 still humming along btw for many users still) then start NEW projects under a new DAW.   If your System is running well, don't upgrade to anymore Windows versions.   YOur music computer SHOULD be dedicated anyway and if not,  get a small notebook to run other generic software and leave your music machine isolated and "frozen"
 

Maybe some are "panicking".  I'm not.  I do, however, have concerns for projects years from now.  All my work is in Cakewalk so, yes I'll have to maintain a PC with a copy of Sonar Platinum on it for the duration.  The real life issues are motherboards dying and then no way- or a very painful way- to re-install old OS's.  (Think if we needed to re-install Windows '98 on a computer...).  So there are some very real concerns. 
 

stxx
Just keep using sonar as it will continue to work. Not sure why the panic.  I still have some software tools that have been running on Windows 8 that started back on Win 95.    If people are that concerned over the future and afraid it will suddenly break (Sonar 8.5 still humming along btw for many users still) then start NEW projects under a new DAW.   If your System is running well, don't upgrade to anymore Windows versions.   YOur music computer SHOULD be dedicated anyway and if not,  get a small notebook to run other generic software and leave your music machine isolated and "frozen"
 

For me personally, as someone who writes music in his DAW, it has never been as simple as just "start NEW projects under a new DAW". I have tens of Sonar projects - maybe even a hundred - that are just full of ideas and potential arrangements, many of which in future will become part of albums I release. I don't expect Sonar Platinum to stop working any time soon. But, what I do expect is to end up with a new computer at some point, and maybe re-installing SPlat onto there will be a problem, if the authentication servers aren't working, or if the downloads aren't available, or if the latest version of Windows at the time makes it hard to run SPlat, or if my new audio interface isn't compatible, or for any number of other unlikely-but-possible unknowns that are hard to recover from. So, I'm migrating projects as I go along

Kylotan

1. S1 doesn't have track templates but it does have FX Chains, so if you have tracks or track templates with a lot of FX involved, consider making and saving FX Chains to speed up the process of setting up these tracks. If you created new per-effect presets as mentioned above this can go pretty quickly

No track templates. That sucks. I love my track templates - I use them extensively.  I'd have to set them up as projects in Studio One? (if I go to S1 of course)