# Migrating Extensions **URL:** \ **Category:** Radiant CMS\ **Created:** [November 19, 2007, 7:05pm UTC](https://www.ruby-forum.com/t/migrating-extensions/120682 "2007-11-19T19:05:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\ **Post date:** [November 19, 2007, 7:05pm UTC](https://www.ruby-forum.com/t/migrating-extensions/120682/1 "2007-11-19T19:05:26Z")
What is the radiant method for reverse migrations? I would have guessed: rake db:migrate:extensions:my\_extension\_name VERSION=XXX but of course this does not work. This also brings up a second issue: Is it even possible to migrate one extension without doing them all? Again, I would have guessed something like the following would be possible: rake db:migrate:extensions:my\_extension\_name -Chris ---
**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\ **Post date:** [November 19, 2007, 7:34pm UTC](https://www.ruby-forum.com/t/migrating-extensions/120682/2 "2007-11-19T19:34:49Z")
On Nov 19, 2007 7:04 PM, Chris P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > What is the radiant method for reverse migrations? > > I would have guessed: > rake db:migrate:extensions:my\_extension\_name VERSION=XXX You should be able to do something like this: rake radiant:extensions:extension\_name:migrate VERSION=0 ---
**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\ **Post date:** [November 20, 2007, 11:09am UTC](https://www.ruby-forum.com/t/migrating-extensions/120682/3 "2007-11-20T11:09:13Z")
Execute “rake -T” on your app root to see all the available tasks. Radiant’s rakefile is clever and catches the extension’s rake tasks automagically. ``` /AITOR ```