xtc2oxid – Migrating xt:commerce Shops to OXID

Itratos from Bamberg has done a great job with coming up with a Migration-Script for shops moving from xt:commerce shop software to OXID (currently version 4.2).

Command Line (CLI) and Web-based Script

Two variants of the script are available, each for a web-browser based invocation and a command-line (CLI) invocation.  We used CLI method.

console@host:~/xtc2oxidmodule$ php xtc2oxid_commandline.php &

Skip the & at the end of the command if you wish to see the live output on the console, else the command will run in the background.  For the first time you run the script, it isn’t a bad idea to view the live output on the console.

Glitches

A few initial glitches had to be overcome, primarily because the PHP CLI binary on the migration machine was of PHP4, which rendered calls to native OXID classes unsuccessful.  Replacing the php4-cli package from our Debian 5.0 Lenny machine with php5-cli fixed the problem.  Remarks in this post pertain to the CLI-method.

Variables related to the migration environment, such as paths of the existing xt:commerce shop, the target OXID shop, database settings etc. are stored in a handy _config.php, placed in the same directory as the xtc2oxid_commandline.php script.

Types of Data Migrated

  • Customer/Buyer data with all addresses
  • Products, including pictures and variants
  • Categories
  • Manufacturers
  • Orders
  • Newsletter and newsletter-subscribers

User Data

User-data (shop buyers) is migrated as well.  However it is required that users are informed of new passwords, since the database storage encryption is different in xt:commerce and OXID (uses md5).

About euroblaze’s OXID Migration Services

euroblaze provides migration-services for OXID Shops.  We migrate other shops systems (such as xt:commerce) to OXID e-Sales, or older versions of OXID (OXID-2, OXID-3, OXID Mietshop/SaaS), to  newer versions.

7 Comments
  1. Some of the questions we are facing are:

    – Is the active/inactive state of variants preserved?
    – How to deal with the thumbnail product images

  2. The xtc2oxid script migrates the Article "Short Description" field with HTML tags (which are permissible in XTC, but not in OXID)

  3. PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/imap.so' – /usr/lib/php5/20060613+lfs/imap.so: cannot open shared object file: No such file or directory in Unknown on line 0

    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/mcrypt.so' – /usr/lib/php5/20060613+lfs/mcrypt.so: cannot open shared object file: No such file or directory in Unknown on line 0

  4. Some of the things we are "discovering" after an xtc2oxid data migration using the Itratos script are going to be posted as multiple-comments here…

  5. Can Customer Groups (Kundengruppierung) be preserved after the migration?

  6. Would be great to have the active/inactive binary setting preserved after migration

  7. This error shows consistently when script is started:

    —ottawa:~/xtc2oxidmodule$ PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/imap.so' – /usr/lib/php5/20060613+lfs/imap.so: cannot open shared object file: No such file or directory in Unknown on line 0
    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/mcrypt.so' – /usr/lib/php5/20060613+lfs/mcrypt.so: cannot open shared object file: No such file or directory in Unknown on line 0

Leave a Reply