81
Best Practices for Migrating a Legacy-Based CMS to Drupal Paul Chason Managing Partner Mediacurrent Bryan House Marketing Director Acquia

Best Practices for Migrating a Legacy-Based CMS to Drupal

  • Upload
    acquia

  • View
    5.334

  • Download
    1

Embed Size (px)

Citation preview

Page 1: Best Practices for Migrating a Legacy-Based CMS to Drupal

Best Practices for Migrating a Legacy-Based CMS to Drupal

Paul ChasonManaging Partner

Mediacurrent

Bryan HouseMarketing Director

Acquia

Page 2: Best Practices for Migrating a Legacy-Based CMS to Drupal

© 2009 Acquia, Inc. All rights reserved.

Agenda

IntroductionPreparing to migrate legacy contentUnderstanding Drupal conceptsImporting content into DrupalCase study – In-Fisherman.comHow Acquia can helpQuestions

Page 3: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Gaining Market Momentum

Page 4: Best Practices for Migrating a Legacy-Based CMS to Drupal

Social Publishing Software =>Participation-Driven

Websites

blogs /wikis

forums / comments

ratings

tagging

users

social networks

workflow

taxonomy

search

RSS

content

analytics

ContentMgmtSystems

SocialSoftware

Tools

SocialPublishingSystems

Page 5: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal & ROI

Reduce costs– Zero $$ software

licensing– Reduced maintenance

costs

Deploy websites faster– Modular architecture– Configurable, not custom

Repeatable infrastructure– Multisite support– Turnkey site deployment

Page 6: Best Practices for Migrating a Legacy-Based CMS to Drupal

© 2009 Acquia, Inc. All rights reserved.

Mediacurrent

Paul Chason– Managing Director, Mediacurrent

Page 7: Best Practices for Migrating a Legacy-Based CMS to Drupal

Mediacurrent Company Overview

Page 8: Best Practices for Migrating a Legacy-Based CMS to Drupal

Mediacurrent Company Overview

Atlanta, GA based web consultancy exclusively focused in Drupal

Page 9: Best Practices for Migrating a Legacy-Based CMS to Drupal

Mediacurrent Company Overview

Atlanta, GA based web consultancy exclusively focused in Drupal

Full-service Drupal provider – front and back end development; specialize in enterprise level Drupal implementations

Page 10: Best Practices for Migrating a Legacy-Based CMS to Drupal

Mediacurrent Company Overview

Atlanta, GA based web consultancy exclusively focused in Drupal

Full-service Drupal provider – front and back end development; specialize in enterprise level Drupal implementations

Acquia Gold Development Partner

Page 11: Best Practices for Migrating a Legacy-Based CMS to Drupal

Mediacurrent Company Overview

Atlanta, GA based web consultancy exclusively focused in Drupal

Full-service Drupal provider – front and back end development; specialize in enterprise level Drupal implementations

Acquia Gold Development Partner

Page 12: Best Practices for Migrating a Legacy-Based CMS to Drupal

Define Drupal Site Requirements

Page 13: Best Practices for Migrating a Legacy-Based CMS to Drupal

Define Drupal Site Requirements

Determine how your users will interact with the legacy data on the new site

Page 14: Best Practices for Migrating a Legacy-Based CMS to Drupal

Define Drupal Site Requirements

Determine how your users will interact with the legacy data on the new site

Is there any legacy data that can be leveraged to create new content? Example: using an address record to populate a Google Map

Page 15: Best Practices for Migrating a Legacy-Based CMS to Drupal

Define Drupal Site Requirements

Determine how your users will interact with the legacy data on the new site

Is there any legacy data that can be leveraged to create new content? Example: using an address record to populate a Google Map

Will content need to be re-categorized in the new site?

Page 16: Best Practices for Migrating a Legacy-Based CMS to Drupal

Sizing Up Legacy Content

Page 17: Best Practices for Migrating a Legacy-Based CMS to Drupal

Sizing Up Legacy Content

Where does your content “live” and what format is it in?

Page 18: Best Practices for Migrating a Legacy-Based CMS to Drupal

Sizing Up Legacy Content

Where does your content “live” and what format is it in?

Determine which parts of legacy content will be used on the new site and what new meta data will possibly need to be added during the export

Page 19: Best Practices for Migrating a Legacy-Based CMS to Drupal

Prepare Content Export

Page 20: Best Practices for Migrating a Legacy-Based CMS to Drupal

Prepare Content Export

Generate CSV file containing legacy content data (most Drupal contributed modules have CSV support)

Page 21: Best Practices for Migrating a Legacy-Based CMS to Drupal

Prepare Content Export

Generate CSV file containing legacy content data (most Drupal contributed modules have CSV support)

Make sure steps to generate CSV file are well-documented, especially if making complex data transformations in the export logic

Page 22: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Content Basics

Page 23: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Content Basics

A “node” in Drupal is the general term for describing a unit of content. A node can be a story, blog post or page for example.

Page 24: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Content Basics

A “node” in Drupal is the general term for describing a unit of content. A node can be a story, blog post or page for example.

A “content type” is a collection of fields that make up a node. Nodes can have one or more data fields and the content type serves as a container for those fields.

Page 25: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Content BasicsContent Type Node

Title field

Page 26: Best Practices for Migrating a Legacy-Based CMS to Drupal

How is Legacy Content Stored in Drupal?

Page 27: Best Practices for Migrating a Legacy-Based CMS to Drupal

How is Legacy Content Stored in Drupal?

Imported data is matched to a specific content type by way of a Drupal module or custom PHP / MySQL scripts

Page 28: Best Practices for Migrating a Legacy-Based CMS to Drupal

How is Legacy Content Stored in Drupal?

Imported data is matched to a specific content type by way of a Drupal module or custom PHP / MySQL scripts

Legacy content fields map to various content types’ fields such as text, numbers, checkboxes / radio button groups, categories, images, etc.

Page 29: Best Practices for Migrating a Legacy-Based CMS to Drupal

How is Legacy Content Stored in Drupal?

Imported data is matched to a specific content type by way of a Drupal module or custom PHP / MySQL scripts

Legacy content fields map to various content types’ fields such as text, numbers, checkboxes / radio button groups, categories, images, etc.

Each row of the CSV export file becomes a node in Drupal’s database

Page 30: Best Practices for Migrating a Legacy-Based CMS to Drupal

Methods for Importing Content to Drupal

Page 31: Best Practices for Migrating a Legacy-Based CMS to Drupal

Methods for Importing Content to Drupal

Drupal contributed modules such as Node Import, Migrate and Transformations. See http://groups.drupal.org/node/21338 for comparison of various Drupal data export/import modules

Page 32: Best Practices for Migrating a Legacy-Based CMS to Drupal

Methods for Importing Content to Drupal

Drupal contributed modules such as Node Import, Migrate and Transformations. See http://groups.drupal.org/node/21338 for comparison of various Drupal data export/import modules

Custom PHP scripts (it’s possible to bootstrap just the database layer of Drupal to cut down on the code required) or custom Drupal modules

Page 33: Best Practices for Migrating a Legacy-Based CMS to Drupal

Methods for Importing Content to Drupal

Drupal contributed modules such as Node Import, Migrate and Transformations. See http://groups.drupal.org/node/21338 for comparison of various Drupal data export/import modules

Custom PHP scripts (it’s possible to bootstrap just the database layer of Drupal to cut down on the code required) or custom Drupal modules

Custom MySQL scripts for database to database migration

Page 34: Best Practices for Migrating a Legacy-Based CMS to Drupal

Advantages of Migrating to Open-Source Drupal at the Enterprise Level

Page 35: Best Practices for Migrating a Legacy-Based CMS to Drupal

Advantages of Migrating to Open-Source Drupal at the Enterprise Level

Scalable

Page 36: Best Practices for Migrating a Legacy-Based CMS to Drupal

Advantages of Migrating to Open-Source Drupal at the Enterprise Level

Scalable Social networking feature-rich

Page 37: Best Practices for Migrating a Legacy-Based CMS to Drupal

Advantages of Migrating to Open-Source Drupal at the Enterprise Level

Scalable Social networking feature-rich

Flexible,easy to

customize

Page 38: Best Practices for Migrating a Legacy-Based CMS to Drupal

Advantages of Migrating to Open-Source Drupal at the Enterprise Level

Scalable Social networking feature-rich

Flexible,easy to

customize

$Lower total

cost of ownership

Page 39: Best Practices for Migrating a Legacy-Based CMS to Drupal

Case Study: In-Fisherman.com

Page 40: Best Practices for Migrating a Legacy-Based CMS to Drupal

Case Study: In-Fisherman.com

Complements the print magazine In-fisherman

Page 41: Best Practices for Migrating a Legacy-Based CMS to Drupal

Case Study: In-Fisherman.com

Complements the print magazine In-fisherman

Initially built with proprietary CMS

Page 42: Best Practices for Migrating a Legacy-Based CMS to Drupal

Case Study: In-Fisherman.com

Complements the print magazine In-fisherman

Initially built with proprietary CMS

Averages 67,789 user visits, 266,379 page visits, and an average of 4:1 page visits/user visits per month

Page 43: Best Practices for Migrating a Legacy-Based CMS to Drupal

Why Did In-Fisherman.com Choose Drupal?

Page 44: Best Practices for Migrating a Legacy-Based CMS to Drupal

Why Did In-Fisherman.com Choose Drupal?

Multi-site / multi-database capability

Page 45: Best Practices for Migrating a Legacy-Based CMS to Drupal

Why Did In-Fisherman.com Choose Drupal?

Multi-site / multi-database capability

Ability to run forums (forum module) and website on same platform with single sign-on capability

Page 46: Best Practices for Migrating a Legacy-Based CMS to Drupal

Why Did In-Fisherman.com Choose Drupal?

Multi-site / multi-database capability

Ability to run forums (forum module) and website on same platform with single sign-on capability

Built-in social networking features offering commenting, tagging and user generated content

Page 47: Best Practices for Migrating a Legacy-Based CMS to Drupal

Why Did In-Fisherman.com Choose Drupal?

Multi-site / multi-database capability

Ability to run forums (forum module) and website on same platform with single sign-on capability

Built-in social networking features offering commenting, tagging and user generated content

Active development community

Page 48: Best Practices for Migrating a Legacy-Based CMS to Drupal

Lessons Learned from In-Fisherman.com

Page 49: Best Practices for Migrating a Legacy-Based CMS to Drupal

Lessons Learned from In-Fisherman.com

Challenge

Migrate 1500+ articles from Filemaker Pro database to

Drupal 6 for In-Fisherman.com redesign

Page 50: Best Practices for Migrating a Legacy-Based CMS to Drupal

Obstacles

Page 51: Best Practices for Migrating a Legacy-Based CMS to Drupal

Obstacles

Filemaker Pro only exported XML data, needed to transform data to CSV format

Page 52: Best Practices for Migrating a Legacy-Based CMS to Drupal

Obstacles

Filemaker Pro only exported XML data, needed to transform data to CSV format

Image files stored in disparate file system with no URL pointer stored in Filemaker Pro

Page 53: Best Practices for Migrating a Legacy-Based CMS to Drupal

Obstacles

Filemaker Pro only exported XML data, needed to transform data to CSV format

Image files stored in disparate file system with no URL pointer stored in Filemaker Pro

Compromised data integrity

Page 54: Best Practices for Migrating a Legacy-Based CMS to Drupal

Obstacles

Filemaker Pro only exported XML data, needed to transform data to CSV format

Image files stored in disparate file system with no URL pointer stored in Filemaker Pro

Compromised data integrity

Page 55: Best Practices for Migrating a Legacy-Based CMS to Drupal

Solution

Page 56: Best Practices for Migrating a Legacy-Based CMS to Drupal

Solution

Transform XML content to CSV format with custom PHP script

Page 57: Best Practices for Migrating a Legacy-Based CMS to Drupal

Solution

Transform XML content to CSV format with custom PHP script

Insert Drupal image filepath during transformation and transfer image files via FTP to application server

Page 58: Best Practices for Migrating a Legacy-Based CMS to Drupal

Solution

Customize Node Import module to handle importing CSV records into Drupal

Page 59: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal’s Impact on In-Fisherman.com

Page 60: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal’s Impact on In-Fisherman.com

Flexible web platform offering ability to easily add new features without compromising core business logic

Page 61: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal’s Impact on In-Fisherman.com

Flexible web platform offering ability to easily add new features without compromising core business logic

Faster page loads

Page 62: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal’s Impact on In-Fisherman.com

Flexible web platform offering ability to easily add new features without compromising core business logic

Faster page loads

Better SEO strategy: SEO-friendly URL’s via the Pathauto module, HTML title and meta-tag control at the article level

Page 63: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal’s Impact on In-Fisherman.com

Flexible web platform offering ability to easily add new features without compromising core business logic

Faster page loads

Better SEO strategy: SEO-friendly URL’s via the Pathauto module, HTML title and meta-tag control at the article level

Biggest ROI: no enterprise-level licensing fees

Page 64: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Page 65: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Ensure all project stakeholders are familiar with the structure of the legacy content and its intended use on the new site

Page 66: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Ensure all project stakeholders are familiar with the structure of the legacy content and its intended use on the new site

Run several “test” imports

Page 67: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Ensure all project stakeholders are familiar with the structure of the legacy content and its intended use on the new site

Run several “test” imports

Make sure a Drupal consultant is available during the final import

Page 68: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Ensure all project stakeholders are familiar with the structure of the legacy content and its intended use on the new site

Run several “test” imports

Make sure a Drupal consultant is available during the final import

Break down content migration tasks into small manageable steps

Page 69: Best Practices for Migrating a Legacy-Based CMS to Drupal

Keys to a Successful Import

Ensure all project stakeholders are familiar with the structure of the legacy content and its intended use on the new site

Run several “test” imports

Make sure a Drupal consultant is available during the final import

Break down content migration tasks into small manageable steps

Document what works along the way

Page 70: Best Practices for Migrating a Legacy-Based CMS to Drupal

Interested in Migrating Your Current CMS to Drupal?

Page 71: Best Practices for Migrating a Legacy-Based CMS to Drupal

Interested in Migrating Your Current CMS to Drupal?

Contact Mediacurrent at www.mediacurrent.com/contact to schedule a discovery call!

Page 72: Best Practices for Migrating a Legacy-Based CMS to Drupal

Interested in Migrating Your Current CMS to Drupal?

Contact Mediacurrent at www.mediacurrent.com/contact to schedule a discovery call!

For help on how to build an enterprise-level website with Drupal, go to

www.mediacurrent.com/download-white-paper

Page 73: Best Practices for Migrating a Legacy-Based CMS to Drupal

Acquia is Your Drupal Guide

What modules should we install?

Where do we get professional support?

How do we host our site? Will it scale?

...Where do we start?

Page 74: Best Practices for Migrating a Legacy-Based CMS to Drupal

Acquia Network Subscriptions

FitnessDiagnosticsResponse

Page 75: Best Practices for Migrating a Legacy-Based CMS to Drupal

Drupal Support, When You Need It20+ Drupal engineers on staff24x7 emergency availabilityDefined SLAsTicket tracking until satisfied resolution

Page 76: Best Practices for Migrating a Legacy-Based CMS to Drupal

Recommendations For Drupal Fitness

Advisory supportBest practicesInformation architecturePerformance tuningModule selectionRemote administration

Page 77: Best Practices for Migrating a Legacy-Based CMS to Drupal

On Demand Visibility and DiagnosticsHealth dashboardHeartbeat monitoringSite statisticsSite profile informationRemote cron

Page 78: Best Practices for Migrating a Legacy-Based CMS to Drupal

one-stop shopDrupal infrastructure + application support

Page 79: Best Practices for Migrating a Legacy-Based CMS to Drupal

Bring vertical and technical solution expertise to build websites that meet client

specifications.

Using Drupal to address unique business and technical requirements on the Web.

Acquia Network subscriptions provide enterprise-class support, hosting and network services to ensure websites meet business objectives.

Acquia

Drupal site owners Acquia Gold Partner

Mediacurrent

Customer Success

Helping Organizations Succeed with Drupal

Productive partnerships focused on customer success

Page 80: Best Practices for Migrating a Legacy-Based CMS to Drupal

Benefits of Using Drupal CMS

Accomplish more with less

Harness community-driven technology innovation

Engage your audience

Page 81: Best Practices for Migrating a Legacy-Based CMS to Drupal

© 2009 Acquia, Inc. All rights reserved.

Questions

For more information, visit each of us at:– http://acquia.com/community– http://twitter.com/acquia– http://twitter.com/mediacurrent

Contact Acquia:– [email protected]– 888-9-ACQUIA

Contact Mediacurrent:– [email protected]– 866-507-0005

Sign up for a free 30-day Acquia Network trial– http://acquia.com/trial