Now here's what. I recorded my 10 row matrix performance with all 10 rows routed to a single audio track. Sonar put them as 10 take lanes under the audio track. I realize that was foolish of me and I should have routed each of the matrix row to a separate audio track. 
Well, but whats done is done. The matrix performance is captured so well that I don't want to have to record again.
 
Is there a way to quickly and easily move the 10 take lanes to 10 separate audio tracks ? Please help.
 

I don't think so. You have to drag them individually. If you find a way I'd love to hear it.

Same as above; me experience is you need to Shift+drag individually.
A macro command to convert multiple take lanes to individual tracks would be a nice function, but not sure how many would find it useful. All ears if anyone has found a better way.

Logic does this, by the way.

I could not find a feature request for this feature, so I added the following "Idea" in the Bakery.  If you like it, please go over to the Bakery in the Ideas section by clicking on the following link, and vote it up.

Function to explode take lane contents to new tracks

----------------------------------------------------------------------------------------------------
When a user wants to convert a track containing multiple takes into new tracks for each take, they currently must manually add a sufficient number of tracks to contain each take, name the new tracks appropriately and then manually drag each take to the correct new track.
This process is manually intensive and error-prone.
SONAR should have a single built-in function that would allow the user to automatically "explode" or "unpack" each take lane into a new separate track.  This feature is already available in a number of competing DAWs.
 
Adding this function would add significant value to the existing comping and takes system.
Proposed Workflow:
1.  User selects the parent track and uses the existing right click context menu to select the new function.
2.  SONAR automatically creates new individual tracks that match the count of the existing take lanes belonging to the parent track.
3.  SONAR sets the I/O in the new tracks to match the parent track.
4.  SONAR names each new track based on the original parent track name concatenated with a hypen "-" and each take lane name.
Example:
  Parent track:   Lead Guitar               Take lane names:  T1, T2, T3
  New tracks:  Lead Guitar - T1, Lead Guitar - T2, Lead Guitar - T3
5.  SONAR copies the existing take lane contents to the appropriate new tracks.
6.  SONAR leaves the original parent and take lanes in place, optionally muting the parent track.

Make 9 clones of the track.  Then go through each track's 10 take lanes, and delete all but one take lane (leave a different take lane in each track.)  You now have a separate track for each take.
 
I like to do this with vocal takes, after editing out the takes I don't want.  Makes for nice multi-voicing where needed, allows separate effects/EQ/etc of each .  I usually send all the tracks to a patch point for reverb or other Fx that I want to be used across all of the takes.

I'm trying to figure out the use case for this. Seems to me you use Take Lanes either for comping, or because you want to process a bunch of tracks with a single FX Rack. The only common application I can think of is if you were recording individual/different drum parts on each take, and then wanted to explode them to separate tracks so each take could be processed separately.

IIRC, you can copy the lanes, then paste them into a new audio track and all will then paste as tracks except for either the first or last (I cannot remember which now). That oddball track then needs to be inserted/copied again.
 
On the other side, I may be confusing this with copying tracks into lanes... one of the two exhibited the above behavior.

Sanderxpander
I don't think so. You have to drag them individually. If you find a way I'd love to hear it.

Nope  not yet at least.
 
I had to do it the obvious way of dragging each take lane to a new track. This was fine as I had only 10 rows in the matrix which went in as 10 take lanes (so had to do it 9 times). Its only if one has a lot more take lanes and this approach can be cumbersome.
 
But then, as Craig said, it depends on the use case. In my particular case here, I would care to ensure in future that each of my matrix rows is routed to a separate audio track for recording so that the issue of take lanes doesn't arise.

If I found myself doing this too often, I would probably create an autohotkey script to bounce the lanes to tracks. The process would require manually soloing each lane and then a key combination to run the script,