Migrating existing auth.User data to new Django 1.5 custom user model?

Question

I\'d prefer not to destroy all the users on my site. But I want to take advantage of Django 1.5\'s custom pluggable user model. Here\'s my new user model:

Answer 1

We decided to switch to a custom user model in our Django 1.6/Django-CMS 3 project, perhaps a little bit late because we had data in our database that we didn't want to lose (some CMS pages, etc).

After we switched AUTH_USER_MODEL to our custom model, we had a lot of problems that we hadn't anticipated, because a lot of other tables had foreign keys to the old auth_user table, which wasn't deleted. So although things appeared to work on the surface, a lot of things broke underneath: publishing pages, adding images to pages, adding users, etc. because they tried to create an entry in a table that still had a foreign key to auth_user, without actually inserting a matching record into auth_user.

We found a quick and dirty way to rebuild all the tables and relations, and copy our old data across (except for users):

• do a full backup of your database with mysqldump
• do another backup with no CREATE TABLE statements, and excluding a few tables that won't exist after the rebuild, or will be populated by syncdb --migrate on a fresh database:
  • south_migrationhistory
  • auth_user
  • auth_user_groups
  • auth_user_user_permissions
  • auth_permission
  • django_content_types
  • django_site
  • any other tables that belong to apps that you removed from your project (you might only find this out by experimenting)
• drop the database
• recreate the database (e.g. manage.py syncdb --migrate)
• create a dump of the empty database (to make it faster to go round this loop again)
• attempt to load the data dump that you created above
• if it fails to load because of a duplicate primary key or a missing table, then:
  • edit the dump with a text editor
  • remove the statements that lock, dump and unlock that table
  • reload the empty database dump
  • try to load the data dump again
  • repeat until the data dump loads without errors

The commands that we ran (for MySQL) were:

mysqldump <database> > ~/full-backup.sql
mysqldump <database> \
    --no-create-info \
    --ignore-table=<database>.south_migrationhistory \
    --ignore-table=<database>.auth_user \
    --ignore-table=<database>.auth_user_groups \
    --ignore-table=<database>.auth_user_user_permissions \
    --ignore-table=<database>.auth_permission \
    --ignore-table=<database>.django_content_types \
    --ignore-table=<database>.django_site \
> ~/data-backup.sql

./manage.py sqlclear
./manage.py syncdb --migrate
mysqldump <database> > ~/empty-database.sql

./manage.py dbshell < ~/data-backup.sql

(edit ~/data-backup.sql to remove data dumped from a table that no longer exists)

./manage.py dbshell < ~/empty-database.sql
./manage.py dbshell < ~/data-backup.sql

(repeat until clean)

Answer 2

My incredibly lazy way of doing this:

1. Create a new model (User), extending AbstractUser. Within new model, in it's Meta, override db_table and set to 'auth_user'.

2. Create an initial migration using South.

3. Migrate, but fake the migration, using --fake when running migrate.

4. Add new fields, create migration, run it normally.

This is beyond lazy, but works. You now have a 1.5 compliant User model, which just uses the old table of users. You also have a proper migration history.

You can fix this later on with manual migrations to rename the table.

Answer 3

I got tired of struggling with South so I actually ended up doing this differently and it worked out nicely for my particular situation:

First, I made it work with ./manage.py dumpdata, fixing up the dump, and then ./manage.py loaddata, which worked. Then I realized I could do basically the same thing with a single, self-contained script that only loads necessary django settings and does the serialization/deserialization directly.

Self-contained python script

## userconverter.py ##

import json
from django.conf import settings

settings.configure(
    DATABASES={ 
            # copy DATABASES configuration from your settings file here, or import it directly from your settings file (but not from django.conf.settings) or use dj_database_url
            },
    SITE_ID = 1, # because my custom user implicates contrib.sites (which is why it's in INSTALLED_APPS too)
    INSTALLED_APPS = ['django.contrib.sites', 'django.contrib.auth', 'myapp'])

# some things you have to import after you configure the settings
from django.core import serializers
from django.contrib.auth.models import User

# this isn't optimized for huge amounts of data -- use streaming techniques rather than loads/dumps if that is your case
old_users = json.loads(serializers.serialize('json', User.objects.all()))
for user in old_users:
    user['pk'] = None
    user['model'] = "myapp.siteuser"
    user['fields']["site"] = settings['SITE_ID']

for new_user in serializers.deserialize('json', json.dumps(old_users)):
    new_user.save()

With dumpdata/loaddata

I did the following:

1) ./manage.py dumpdata auth.User

2) Script to convert auth.user data to new user. (or just manually search and replace in your favorite text editor or grep) Mine looked something like:

def convert_user_dump(filename, site_id):
    file = open(filename, 'r')
    contents = file.read()
    file.close()
    user_list = json.loads(contents)
    for user in user_list:
        user['pk'] = None  # it will auto-increment
        user['model'] = "myapp.siteuser"
        user['fields']["site"] = side_id
    contents = json.dumps(user_list)
    file = open(filename, 'w')
    file.write(contents)
    file.close()

3) ./manage.py loaddata filename

4) set AUTH_USER_MODEL

*Side Note: One critical part of doing this type of migration, regardless of which technique you use (South, serialization/modification/deserialization, or otherwise) is that as soon as you set AUTH_USER_MODEL to your custom model in the current settings, django cuts you off from auth.User, even if the table still exists.*

Answer 4

I think you've correctly identified that a migration framework like South is the right way to go here. Assuming you're using South, you should be able to use the Data Migrations functionality to port the old users to your new model.

Specifically, I would add a forwards method to copy all rows in your user table to the new table. Something along the lines of:

def forwards(self, orm):
    for user in orm.User.objects.all():
        new_user = SiteUser(<initialize your properties here>)
        new_user.save()

You could also use the bulk_create method to speed things up.

Answer 5

South is more than able to do this migration for you, but you need to be smart and do it in stages. Here's the step-by-step guide: (This guide presupposed you subclass AbstractUser, not AbstractBaseUser)

1. Before making the switch, make sure that south support is enabled in the application that contains your custom user model (for the sake of the guide, we'll call it accounts and the model User). At this point you should not yet have a custom user model.

   $ ./manage.py schemamigration accounts --initial
   Creating migrations directory at 'accounts/migrations'...
   Creating __init__.py in 'accounts/migrations'...
   Created 0001_initial.py.
   
   $ ./manage.py migrate accounts [--fake if you've already syncdb'd this app]
    Running migrations for accounts:
    - Migrating forwards to 0001_initial.
    > accounts:0001_initial
    - Loading initial data for accounts.
   

2. Create a new, blank user migration in the accounts app.

   $ ./manage.py schemamigration accounts --empty switch_to_custom_user
   Created 0002_switch_to_custom_user.py.
   

3. Create your custom User model in the accounts app, but make sure it is defined as:

   class SiteUser(AbstractUser): pass
   

4. Fill in the blank migration with the following code.

   # encoding: utf-8
   from south.db import db
   from south.v2 import SchemaMigration
   
   class Migration(SchemaMigration):
   
       def forwards(self, orm):
           # Fill in the destination name with the table name of your model
           db.rename_table('auth_user', 'accounts_user')
           db.rename_table('auth_user_groups', 'accounts_user_groups')
           db.rename_table('auth_user_user_permissions', 'accounts_user_user_permissions')
   
       def backwards(self, orm):
           db.rename_table('accounts_user', 'auth_user')
           db.rename_table('accounts_user_groups', 'auth_user_groups')
           db.rename_table('accounts_user_user_permissions', 'auth_user_user_permissions')
   
       models = { ....... } # Leave this alone
   

5. Run the migration

   $ ./manage.py migrate accounts
    - Migrating forwards to 0002_switch_to_custom_user.
    > accounts:0002_switch_to_custom_user
    - Loading initial data for accounts.
   

6. Make any changes to your user model now.

   # settings.py
   AUTH_USER_MODEL = 'accounts.User'
   
   # accounts/models.py
   class SiteUser(AbstractUser):
       site = models.ForeignKey(Site, null=True)
   

7. create and run migrations for this change

   $ ./manage.py schemamigration accounts --auto
    + Added field site on accounts.User
   Created 0003_auto__add_field_user_site.py.
   
   $ ./manage.py migrate accounts
    - Migrating forwards to 0003_auto__add_field_user_site.
    > accounts:0003_auto__add_field_user_site
    - Loading initial data for accounts.
   

Honestly, If you already have good knowledge of your setup and already use south, It should be as simple as adding the following migration to your accounts module.

# encoding: utf-8
from south.db import db
from south.v2 import SchemaMigration
from django.db import models

class Migration(SchemaMigration):

    def forwards(self, orm):
        # Fill in the destination name with the table name of your model
        db.rename_table('auth_user', 'accounts_user')
        db.rename_table('auth_user_groups', 'accounts_user_groups')
        db.rename_table('auth_user_permissions', 'accounts_user_permissions')
        # == YOUR CUSTOM COLUMNS ==
        db.add_column('accounts_user', 'site_id',
            models.ForeignKey(orm['sites.Site'], null=True, blank=False)))

    def backwards(self, orm):
        db.rename_table('accounts_user', 'auth_user')
        db.rename_table('accounts_user_groups', 'auth_user_groups')
        db.rename_table('accounts_user_user_permissions', 'auth_user_user_permissions')
        # == YOUR CUSTOM COLUMNS ==
        db.remove_column('accounts_user', 'site_id')

    models = { ....... } # Leave this alone

EDIT 2/5/13: added rename for auth_user_group table. FKs will auto update to point at the correct table due to db constraints, but M2M fields' table names are generated from the names of the 2 end tables and will need manual updating in this manner.

EDIT 2: Thanks to @Tuttle & @pix0r for the corrections.