D6 CCK to D7 core field migration docs

imho until this gets completely fleshed out no one other then someone who is Drupal knowledgeable can attempt an upgrade, the information that is available isn't enough to actually get a site up and running.

(reposted to keep everything organized for this issue)

Correct me if I am wrong but this is the existing documentation for CCK > Fields: from http://drupal.org/node/570162

If you were using CCK (and perhaps additional modules) to create fields for your content types, you will need to upgrade the data in those fields as a separate step. Download the Drupal 7 CCK module, and turn on Content Migration. Go to Structure > Migrate Fields or http://example/com/admin/structure/content_migrate for a page to walk you through the migration process. There are now several types of fields in core, but not every type. You might need to download Drupal 7 versions of contributed modules to support other types of fields. (For example, the new References module handles node and user reference fields.)
Do we want to: a) first follow the process at a basic level (with just CCK enabled) and confirm that it works b) follow the same process with other popular CCK contrib modules (i.e. imagefield) enabled

How far down the rabbit hole do we go with this? :)

(repost)

That chunk is copied straight from that page, seems to be the entirety of the official cck > fields documentation right now.

Do you or someone else have to create the page? Do I write offline and forward it to you for approval?

thx arianek, sorry for all the questions but I would rather do it as right as I can the first time

Hope to post at least the beginning something by end of day. Working on it now.

Please take a look at this beginning snippet. I want to make sure I am on the right track.

Data must be migrated to upgrade Content Construction Kit (CCK) in Drupal 6 to Drupal 7 core fields. Much but not all of CCK functionality is now part of Drupal 7 core. Several features require the installation of new separate dedicated 7.x modules. Node reference and user reference now require the References (drupal.org/project/references) module. Content permissions require the Field Permissions module (drupal.org/project/field_permissions). Field Groups require the Field Group (drupal.org/project/field_group) module. The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. (More information on upgrading from Drupal 6 to Drupal 7.)

Upgrade Steps

1. Download latest 7.x CCK module
   
   
   After upgrading to Drupal 7 download the latest 7.x CCK module version (currently 7.x-2.x-dev tar.gz or zip file (drupal.org/CCK). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory.
   
   
   On a typical Unix/Linux command line use the following commands to download and extract:

   wget http://ftp.drupal.org/files/projects/cck-7.x-2.x-dev.tar.gz

   tar -zxvf cck-7.x-2.x-dev.tar.gz

   If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

2. Enable the CCK Content Migrate module
   
   
   Browse to http://yoursitehere.com/admin/modules and check the box next to Content Migrate in the CCK field group. Remember to press save configuration at the bottom of the screen.
   
   
   
3. ...

This looks like a good start! Minor style tweaks can be made once it's in the wiki. Here's a few little things I would change:

Make all project references links, and remove "(currently 7.x-2.x-dev tar.gz or zip file (drupal.org/CCK)"

After upgrading to Drupal 7 download the latest 7.x CCK -> After upgrading to Drupal 7, download the latest 7.x CCK [add comma]

new separate dedicated 7.x modules -> new, dedicated 7.x contrib modules

I had to try this out to see if I meant what I was going to suggest. I like being able to skim for the module names, so I'd suggest highlighting that. I also place http:// in front of all the drupal.org addresses so they'd become automatically clickable, and added a comma or two.

Data must be migrated to upgrade Content Construction Kit (CCK) in Drupal 6 to Drupal 7 core fields. Much but not all of CCK functionality is now part of Drupal 7 core. Several features require the installation of new, dedicated 7.x modules.

• Node reference and user reference now require the References (http://drupal.org/project/references) module.
• Content permissions require the Field Permissions module (http://drupal.org/project/field_permissions).
• Field Groups require the Field Group (http://drupal.org/project/field_group) module.

The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. (More information on upgrading from Drupal 6 to Drupal 7.)

Upgrade Steps

1. Download latest 7.x CCK module
   
   
   After upgrading to Drupal 7, download the latest 7.x CCK module version (http://drupal.org/CCK). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory.
   
   
   On a typical Unix/Linux command line, use the following commands to download and extract:

   wget http://ftp.drupal.org/files/projects/cck-7.x-2.x-dev.tar.gz

   tar -zxvf cck-7.x-2.x-dev.tar.gz

   If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

2. Enable the CCK Content Migrate module
   
   
   Browse to http://yoursitehere.com/admin/modules and check the box next to Content Migrate in the CCK field group. Remember to press save configuration at the bottom of the screen.
   
   
   
3. ...

Feedback please.

Data must be migrated to upgrade Content Construction Kit (CCK) in Drupal 6 to Drupal 7 core fields. Much but not all of CCK functionality is now part of Drupal 7 core. Several features require the installation of new, dedicated 7.x modules.

• Node reference and user reference now require the References (http://drupal.org/project/references) module.
• Content permissions require the Field Permissions module (http://drupal.org/project/field_permissions).
• Field Groups require the Field Group (http://drupal.org/project/field_group) module.

The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. (More information on upgrading from Drupal 6 to Drupal 7.)

Upgrade Steps

1. Download latest 7.x CCK module

   After upgrading to Drupal 7, download the latest 7.x CCK module version (http://drupal.org/CCK). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory.

   On a typical Unix/Linux command line, use the following commands to download and extract:

   wget http://ftp.drupal.org/files/projects/cck-7.x-2.x-dev.tar.gz

   tar -zxvf cck-7.x-2.x-dev.tar.gz

   If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

2. Enable the CCK Content Migrate module

   Browse to http://yoursitehere.com/admin/modules and check the box next to Content Migrate in the CCK field group. Remember to press save configuration at the bottom of the screen.




3. Browse to the Migrate fields page
   
   
   Browse to Structure > Migrate Fields or http://yoursitehere.com/admin/structure/content_migrate for a page to walk you through the migration process.



The Migrate Fields page is divided into 3 sections:

Available fields- Fields that have not been migrated but are available for migration.

Converted fields- Fields that have already been converted. You can choose to roll them back if the conversion did not work correctly. Note that rolling fields back will completely destroy the new field tables. This operation cannot be undone!

Unavailable fields- Fields that cannot be migrated because some modules are missing. Download and install/enable any required modules listed in the Other information column of this section.

4. Download additional modules if necessary

   • References module (http://drupal.org/project/references). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory. On a typical Unix/Linux command line, use the following commands to download and extract:

     wget http://ftp.drupal.org/files/projects/references-7.x-2.x-dev.tar.gz

     tar -zxvf references-7.x-2.x-dev.tar.gz

     If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

   • Field Permissions module (http://drupal.org/project/field_permissions). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory. On a typical Unix/Linux command line, use the following commands to download and extract:

     wget http://ftp.drupal.org/files/projects/field_permissions-7.x-1.0-alpha1.ta...

     tar -zxvf field_permissions-7.x-1.0-alpha1.tar.gz

     If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

   • Field Group module (http://drupal.org/project/field_group). Typically this will be placed in your sites/all/modules or sites/yoursitehere.com/modules directory. On a typical Unix/Linux command line, use the following commands to download and extract:

     wget http://ftp.drupal.org/files/projects/field_group-7.x-1.0-rc2.tar.gz

     tar -zxvf field_group-7.x-1.0-rc2.tar.gz

     If you do not have command line access to your server, download the archive using your web browser, extract it, and then use an FTP client to upload the files to your sites/all/modules or sites/yoursitehere.com/modules directory.

5. Enable additional modules if necessary
   
   
   
   Browse to http://yoursitehere.com/admin/modules and check all applicable boxes in the Fields section. Remember to press save configuration at the bottom of the screen.
6. Migrate fields

Browse to Structure > Migrate Fields or http://yoursitehere.com/admin/structure/content_migrate.

Check the box next to all fields you would like to migrate in the Available fields section.

Press the Migrate selected fields button.

If the migration process is successful you should receive a message detailing that each field was created. All fields should now be listed in the Converted fields section of the page.

The guide itself is great. Adhering to the documentation style guide I would replace the yoursite.com references with example.com, and remove the wget / tar zxvf commands. Those command can be found in more generic documentation.

Apart from that, it's ready to go!

Looks great!!! Well done on the write up. The Migrate module is also a great resource for more advanced migrations.

There isn't any upgrade code in the Field Permissions module, but it should be fine as it uses user_access().

I created Migrating D6 Content Construction Kit (CCK) to D7 Fields and linked to it from Upgrade process.