Best method for porting over old sonar projects to reaper?

I have been setting up reaper over the last few days and it is coming along.  I can get it set up pretty similarly to the workflow I had in sonar.  However, I have lots of old sonar projects that I would like to be able to bring into reaper and continue to develop.  I still have sonar up, running, and updated, but I don't want to get stuck and have to figure it out in a hurry when the time comes that sonar is not running or breaks.
 
OMF formats are not supported by reaper.  I have heard that you can simply drag and drop the waveforms from the gui of sonar into the correct track lane in reaper.  I did try that and had mixed success.  It was fiddly at best.  I have not tried exporting stems from sonar and importing them into reaper, but I might try that. 
 
In any case, it looks like there is no good way to transfer over envelopes, fx bins, pan settings, etc. 
 
How are others here dealing with this issue?
 
Thanks!
 

I am waiting with fingers crossed, but I am also doing a bit of prep in case we are truly screwed. 
Better safe-ish than sorry.
 

Yeah, I have been keeping reaper on my machine too and updating and checking it out for several years as well.
I have always been impressed with how lean and mean it is.  It has come a long way.

I presume he misread your "far from zero" as "close to zero" or something.  Great to hear that you're working on this.  Although I'm sticking with Sonar for the time being, Reaper is the place I'll most likely go if/when the time comes.
 
AMB
 

Hey @azslow3, I do admire your determination to put together a Reaper converter for CWP! I really hope you can pull this off!!!
 
It will make a nice parachute, or plan B, for those that have projects in the CWP format.  Having a 2nd DAW that can open the files will be a reassurance to those who choose to keep running Sonar, which will continue to run for the forseeable future, as far as we know at this time.  Having continued access to one's creative content is essential, to say the least!
 
I have been dabbling with Reaper for the past couple of years, and it is a very impressive, capable DAW package. 
 
But with all that depth it can get rather complex, and the manual is your friend, LOL!
 
I have not chosen to make Reaper my 1st DAW, but have found it useful as a 2nd DAW when trying to understand plugin routing, or testing and comparing plugin functions in Sonar.  There are a few things that I have been able to get working in Reaper, that Sonar wouldn't let me do.
 
The Reaper track paradigm makes more sense that Sonar's for sure.  Flexible track routing is a prime example!  A track is a track! 

I recently (well back on Dec 31, 2017) took an older project from Sonar and one by one rendered the audio tracks to wave. Then one by one I dragged and dropped the waves into Reaper. Lastly I exported all the midi from Sonar with a "Save As", and upon importing that into Reaper, got a dialog where I was able to say expand to individual tracks, so my midi parts each got their own tracks in Reaper. The end result turned out pretty well. It's the first song that plays from the link in my Sig.
 
The original Sonar project was setup to play drums and Hammond B3 to external rack mounted hardware synths that I no longer own. Once I had the tracks in Reaper, I used all new FX and for the drums I used Superior Drummer 2 and Native Instruments B4 organ for the Hammond B3. The new version of this project is light years from what the original Sonar version sounded like.

abacab
Hey @azslow3, I do admire your determination to put together a Reaper converter for CWP! I really hope you can pull this off!!!

The first RPP is already printed
Just with named tracks...
 
At the moment that is command line native Linux executable (60kB in size). So the next step is cross-compiling into Windows Reaper project importer plug-in.
 
Planned features for the first alpha are:
* tempo map
* tracks with clips (only), without care about take lanes, overlapping behavior, etc.
* midi clips
* not looped audio clips
* (may be volume/pan for tracks and corresponding automations)
* (may be simple routing throw buses, to allow at least some audition out of the box, but no sends)
* (may be instantiation of corresponding synths for MIDI tracks, one per track, without preset)
But primary target for the first alpha is making it quick (within days). It will display valuable for me single number: the number of problems within the parser (the parser is complete, it collects almost all information we need, I mean much more than I have just mentioned).
 

I believe his intention is to share the result, though I can't speak for him. But that has certainly been indicated.