# Migrating without loosing data **URL:** \ **Category:** Rails\ **Created:** [July 4, 2008, 9:36am UTC](https://www.ruby-forum.com/t/migrating-without-loosing-data/196735 "2008-07-04T09:36:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vapor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/5e9695/32.png) [@vapor](https://www.ruby-forum.com/u/vapor)\ **Post date:** [July 4, 2008, 9:36am UTC](https://www.ruby-forum.com/t/migrating-without-loosing-data/196735/1 "2008-07-04T09:36:44Z")
I have already created a migration. It adds 5 columns. Now I edit migration file and enter 2 more column. How can I remigrate so that 2 new columns would be added without loosing data with db:migrate:reset? ---
**Author:** ![vapor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/5e9695/32.png) [@vapor](https://www.ruby-forum.com/u/vapor)\ **Post date:** [July 4, 2008, 10:03am UTC](https://www.ruby-forum.com/t/migrating-without-loosing-data/196735/2 "2008-07-04T10:03:31Z")
On Jul 4, 8:36 am, “Vapor …” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I have already created a migration. It adds 5 columns. Now I edit > migration file and enter 2 more column. > > How can I remigrate so that 2 new columns would be added without loosing > data with db:migrate:reset? You can’t (short of dumping the data first and loading it in afterwards or something like that). You’d be better off adding a second migration that adds the extra columns. Fred ---
**Author:** ![vapor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/5e9695/32.png) [@vapor](https://www.ruby-forum.com/u/vapor)\ **Post date:** [July 4, 2008, 10:15am UTC](https://www.ruby-forum.com/t/migrating-without-loosing-data/196735/3 "2008-07-04T10:15:15Z")
We have a policy of never ever editing migrrations, if you do, they become useless… On Jul 4, 9:02 am, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)