As owner of the copyright, it's yours to do with as you think best.
Your best bet for a license is a standard proprietary license. There's enough "free for personal use, commercial use restricted" products out there that it shouldn't be too much hassle to grab a half dozen EULAs and use them as models. Since the rules vary by locality, you'll still want to invest in some competent legal advice and review before you 'go live' with it. Possibly someone at DC has already done this so you could just use their vetted license.
Also check for software industry organizations in your area or up on the web. Most have identified legal resources you can avail yourself of.
As far as CC goes, I don't think it creates any problems. Just pull it and rerelease with the new license attached. Note: if your product is up on any of those big 'free' software sites, it would be a good (as in really good) idea to send them your updated files and license info. Be sure you up the version number on the software to indicate a change, even if it's only to the license. Better still would be to make some changes, no matter how small, in the binaries That provides a nice clean demarcation point between the current released software version and those that came before. Very important if you ever need to try to legally enforce your license.
Easiest right now would be to send an email to the CC people. Explain what you plan to do, and ask if they see any problems with it. If you don't like the answer you get, you can always seek another opinion since their word isn't law.
P.S. If you're developing for the Windows platform, don't neglect to check out Microsoft's BizSpark
program. Link here
. it's a great program if you're a new commercial developer. One of the very few "smart move" bargains out there. Possibly the best thing Microsoft ever came up with for its developers. StackOverflow
had a fairly decent write-up about it here