I'm sorry if this seems like a dumb question, but I've spent the day researching this and feel like I've read every post on the subject. I can't find one that answers this question. I have a LOT of user profile fields attached to my users from Drupal 6. I can't lose this data.

Am I correct that the final answer to do my D6 user profile fields natively upgrade to the D7 account settings manage fields?

It seems like that is what the posts are saying. If that's the case, then the more important question is -- is there any other module or mechanism known to migrate them?

I have checked far and wide for modules for it, including the obvious ones like Migrate and it's accessory modules. None seem to do this. And every post I've read about it jumps many steps by going on to discuss more "radical" options than this - like adding other modules such as profile2 and doing a content_profile migrate from that. I can't find just a simple answer on migrating regular core profile to regular core user fields.

This seems like a pretty obvious way to go, and it seems like there are millions of ways to migrate everything from Ubercart to my cat. So am I crazy to think this should be a contrib migration for this that exists out there somewhere?

I don't mean to sound whiny at all -- I just am really confused by this. And mystified. Possibly even verklempt. Can anyone please answer this for me?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Status: Active » Fixed

See the core modules/profile module. The decision was made to make profile module deprecated in favor of fields. The profile.info file marks the module as hidden. But if you have profile module enabled in D6 it should port to D7 just fine.

I'm not sure of the direction for it in D8; it will likely be removed but you should have time to convert the profile data to fields before that occurs. Sounds like a nifty one version module to do the conversion from profile to fields should someone want to take it on.

somatics’s picture

Thank you for reply. I am aware of what you describe in your post, and my site did reveal and enable the Profile module on its own as part of the upgrade from D6 to D7, so I don't need to un-hide it.

On my site, those profile fields live on their own in Profiles settings page, and then there is a Manage Fields tab on the Account Settings pages, and none of those fields are present on the Manage Fields list. (See attached screenshots.)

The question I am asking is how do I get those Profile fields into the Account fields system.

Anonymous’s picture

Status: Fixed » Active

I have exactly the same question.

Anonymous’s picture

Category: support » feature

The requested feature is support for migrating core Profile fields (that originated in D6) to the User entity's custom D7 fields, in order to allow the (deprecated?) core Profile module to be taken out of the loop.

Anonymous’s picture

Title: User profile data from D6 to D7 user fields? Somehow? Maybe? Please? Anyone? » Migrate Profile fields to Fields and get rid of Profile module.
Version: 7.15 » 8.x-dev
Component: user system » profile.module

Since it is a feature request, the request needs to be made to version 8.x.

I still think that it needs to be a contrib module but let's see what others have to say.

webchick’s picture

In D8, profile module's already gone. #1261576: Profile module data is not upgraded is the critical bug opened for that, which will essentially do what this issue describes, making this one a duplicate.

In D7, we're not going to remove profile module. A migration path from profile fields to normal fields would need to be a contrib module.

Therefore, I think we can close this issue out as "won't fix" or "duplicate" as you wish. If you're interested in helping though, #1261576: Profile module data is not upgraded would LOVE your attention! :D

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Active » Fixed
Related issues: +#2927478: migrate drupal 6 to drupal 7

Migrations exist for the profile module, in the user module. They were added in several commits starting in 2014 and the latest being in 2918. I don't think there is anything to do here. I've added some of the issues as related.

And as webchick points out the profile module is not in Drupal 8.

Therefor, closing this as fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.