Migration from other solutions

This is just an outline, please help completing this page with more details.

It is quite easy to migrate from many other "media" solutions to Scald.

General purpose methods

From IMCE/embedded images modules

Get a list of used files from the text fields/from the {files} table and create scald_image atoms. Enable MEE module.

From File Entity based modules

Add an atom for each file, use hooks to create new atom when a file is added.

From File Field modules

Use Atom Reference module.

Less commonly implemented Migration methods

pre/post Import/Rollback methods

You can execute code before or after an import or rollback operation by implementing the Migration class methods preImport(), postImport(), preRollback(), or postRollback(). Each of these is called once per individual Migration - that is, if you implement preImport() in an article node migration class, it will be called after any previous migrations you're running, and immediately before the first row of your article node migration is called.

Typical actions can be the enabling / disabling of certain modules or changing configurations.

class ArticleMigration implements Migration {
  public function
preImport() {
// Code to execute before first article row is imported
  public function
postImport() {
// Code to execute after the last article row has been imported
  public function
preRollback() {
// Code to execute before first article row is deleted
  public function
postRollback() {
// Code to execute after the last article row has been deleted

A practical example can be found here.

Backup your database and files

Database and custom file backups are essential.

There are many posts in the forum topics about irrecoverable errors, WSOD, database gone fubar etc. There are times when your site goes awry or gets deleted or corrupted, and the only or best choice is to restore it from a backup.

Backup & Migrate

The Backup & Migrate module facilitates emergency recovery and site migration. You can configure it for automatic backups saved to the filesystem - with more frequent backups during development.

You can also create a manual backup before undertaking any complex configuration. That way, you have a "restore point" in case of disaster.

While there may be some issues of security when you save the database and content as a file (you could exclude certain tables, perhaps), the benefits of having a rollback in case of disaster are significant.

Migrating a site

You need to migrate your Drupal site if you change hosts, or if you maintain separate development and live sites. This is an outline of the process – perhaps only a check list – but it includes some steps that are not well described elsewhere. You need to adjust these steps depending on the modules you use and your server environments.

Migrating from Joomla/Mambo

This guideline focuses on migration from Joomla to Drupal (was: Joomla! 1.0.x to Drupal 4.7.x/5.x). It's also aiming to be useful for people who are used to Joomla and want to learn Drupal and vice versa.

Before you start a migration you must understand some differences between both to make sure your migration to be successful:

Migrating to Drupal

This page contains hints and scripts from members of the Drupal community for migrating to Drupal from other content management systems (CMS) weblog, and bulletin board applications. Migrating from other platforms often requires knowledge of PHP and SQL.

Migration involves mapping data fields from the original application's database into Drupal's database. For some applications this can be a simple task, with tools or scripts available to do the migration. Other applications may have complex database schemas, lack documentation, and are uncommon enough that there are no tools available.

The best way to find out if tools or scripts exist for your application is to search on Google. For example a search such as "migrate WordPress Drupal" returns dozens of useful links.

If there are no tools available for migrating from your application to Drupal, you will want to familiarize yourself with Drupal's database schema, as well as the schema of the application you are migrating.

Subscribe with RSS Subscribe to RSS - migration