Migrating from 6.1.6

We have over 7,000 Profiles in our 6.1.6 database, including a few customized fields that are not used "directly" by Dolphin. The profiles migration has been sitting at 2,456 for 2 hours now, and indicates queued/in process. Since SOME of the profiles obviously migrated, I don't think the cronjob is at fault here. What would cause it to pause like this? It's making me wonder whether we should scrap upgrading, simply because our memberbase is too large for a migration.

Also, while waiting for the profiles to migrate, I took a tour of some of the other admin features, specifically the builder-related ones. Does the PageCompose table and others related to the site design/layout transfer over as well, or will that have to be completely redone? If it has to be redone then.... boo on that!!

Thoughts?

The migration module migrates only what you see for the options available, nothing more. If you wish to migrate your web site to the new release, you will have to re-build a bit.

I do not have as much experience as others do on here when it comes to the migration module, so hopefully someone else will be able to join this topic and help you out with why it's not completing the transfer.

Well that's going to be rather time-consuming, hah!

Edited: Looks like sys_page_compose is the new home of website layout under D7... well, at least I can see where to insert stuff from the previous version. I sure hope someone has some insight about the member migration. I *could* do that 'by hand' with sql statements, but really would rather not.

In Dolphin 7, the equivalent is called sys_page_compose (or something along those lines). I don't recall its settings being migrated over, though, unless its under the migration module's list of abilities.

I'm wondering if the profiles table can be migrated in chunks? That is, could I set up the source database with the first 2000 names and run the migration, then wipe out those first 2000 records and load up 2,001 - 4000 and re-migrate... does migration overwrite or append to the D7 Profiles table?

OK, the weirdness continues... someone who had ID #2 on the old (D6) database is now ID #8655 in the new one. That makes it almost useless, because we are using Dolphin to establish referral-based membership, and referrals are tied to their referrees by ID, and if that changes on migration... all the relationships are broken.

Am I misunderstanding what the "migration" process is supposed to do? It seems - pardon my language - retarded to mess with something as basic as Profile data in a manner like this, as part of what SHOULD be an upgrade rather than a replacement. This is frustrating and rather off-putting :(

when I did my migration the member ids remained the same.

It's weird because the admin account created at installation time starts out at ID #1, but when I look in the DB after migration appears to have stalled out, admin is ID #11808 (which would be the next available ID in the old database). So it's almost like some kind of bubble sort is going on during the migration process.

Also, error message which are emailed during migration say things like:

UPDATE `Profiles` SET `ID` = '7576' WHERE `ID` = '7193' Mysql error: Duplicate entry '7576' for key 1

Which to me suggests that the migration process is shuffling around ID numbers. I can't think otherwise why it would be re-assigning ID numbers. Anyone know?

The migration will fail giving duplicate type errors if your D7 database is not 100% empty. You should only have the admin account.

And you are correct, the D7 admin account has its ID changed to the next avalible ID.

Are you running the migration with a live D6 and or D7 database? Are people signing up during the migration?

Nope, not using a live database for either the D6 or D7.

Just an update on my workaround. I migrated over a small chunk of profiles, including the custom fields (not all of which seemed to come over, but see below), then wiped out the database except for admin, and moved the entire old database over with a mysql dump. While importing the dump, I found two fields which didn't come over with the customizer, so just manually added them through phpmyadmin, and then the dump imported.

A little digging around here found a solution on how to convert the old md5 passwords to sha and create a salt for each of them (thanks to the folks who wrote that fix), and ta-dah - all 7000+ profiles moved and logins work.

So for those whose profile migration is timing out or taking forever, I'd recommend going this somewhat more manual route, if you are comfortable enough working with the database more directly than through the Dolphin tools.

I was able to move over the old site content in this manner as well (the Page Blocks). Wasn't sure if there was a migration tool for that, but it didn't matter much because the tables were set up the same, so one dump and import did the trick there. Now we just need to reposition the blocks within the navigator builder.