Now that D6 is no longer supported, it was a must to move D6 sites I maintain to D7. This guide is the recipe to moving simple content with non-complicated CCK fields from D6 site to a D7 site.

Prepare your new site

Create all required content types on the new D7 site. Add all required fields to content types.

Many installations of the Community Media Starterkits include CiviCRM. Therefore, when upgrading the Starterkits you will be responsible for upgrading CiviCRM as well.

Commerce coupon upgrade guide

Commerce coupon beta4 has been out there for a while and the majority of changes have been implemented in the dev version, so if you're upgrading from beta4 to beta5, you may have problems in the process. This page will provide tips and process documentation, feel free to complete it with your use case.

Major changes in the module

The changes happening in this module can be reviewed in more detail in the roadmap issue, but as an outline, this has happened:

• There's now two independent projects for Percentage Coupons and Fixed amount coupons.
• Basic coupon type is not used anymore.
• Coupon log entity has been removed for good.
• Coupon reference has been transformed to Entity Reference.

Upgrade tips

As the changes have happened in a quite long time lapse, you may find some issues in the way, most of them related with the coupon reference fields.
Please review the upgrade path in a sandbox before doing the process in a production site

Though for most of the content it will just work, be ready for some missing (multilingual) data and manual reconfiguration.

The module has been fully reworked (again) to keep up with new Drupal core features. There are new modules and features. Many settings have been changed. So please, read all this page before doing anything.

Some old (multilingual) variable values may be lost as for some cases they have been converted to blocks by Drupal core: Site mission, Site footer. Write down the old values for each language so you can use them later.

Multilingual sites are complex enough and each site is a whole different story. Try the upgrade before with a clone of your production site.

Drupal 7 upgrade notes

• You may lose some string and variable translations in the process so you better get a dump of i18n_variable and export your locale translations for textgroups different than default.
• To upgrade from 6.x, first upgrade to the latest 6.x stable release. To upgrade from 5.x, first upgrade to 6.x, then to 7.x
• Other parts like the multilingual block system have been completely reworked and will need manual reconfiguration. Existing normal blocks won't be lost but the language settings will need manual reconfiguration.

The Internationalization (i18n) package provides full upgrade scripts for a smooth transition from Drupal 5 to Drupal 6. However, due to some multilingual features provided now by Drupal core and that the Internationalization package has been fully reworked, there are some special considerations. So, please, read this page before doing anything.

Drupal 6 upgrade notes

• To upgrade from 5.x, first upgrade to the latest 5.x stable release. To upgrade from 4.x, first upgrade to 5.x, then to 6.x.
• Note that some old features and behaviors have been dropped and replaced by new Drupal 6 multilingual features. This module won't pretend to replace Drupal core available features but to build on them and provide extended ones.
• While the upgrade scripts already work for nodes and taxonomy, there's other data that is simply deleted by the main Drupal 6 core upgrade, like the menu items language.
• Other parts like the multilingual block system have been completely reworked and will need manual reconfiguration. Existing normal blocks won't be lost but the language settings will need manual reconfiguration.