This year Drupal is 17. For over a decade the process of upgrading from one version to another was one of the biggest challenges. With Drupal 8 the ease of upgrading was one of most pleasant surprises. Looks like Drupal is getting out of teenage years and becoming quite a mature entity. By the end of this session you will know how to complete a content upgrade for your Drupal 7 or 6 website, and what is not included. We will do a step-by-step demo of how the migration process goes: Starting with out of the box vanilla Drupal 8 site Connecting to the existing website that you want to upgrade What modules you need for Drupal 8 Blocks, Theme, and Views migrations Options available for moving content from other systems: Feeds (finally ready for Drupal 8), Migrate Plus and other plugins. We will also discuss when you want to upgrade your site and when you want to migrate your site, and variations/combinations of these two cases. Session Takeaway: How and when to upgrade your website to Drupal 8 Expected Attendees: This session is designed for site builders, content managers and strategists who are planning overall site development.

1. CONTENT MIGRATION INTO
DRUPAL8
WITH ONE CLICK EASE
FOR SITE BUILDERS
Case study :: Work in progress
Irina Zaks izaks@stanford.edu
http://fibonacciwebstudio.com/

2. In this presentation
We will talk about
Content Migration Tools We will not present today
 Standard Upgrade via
web interface
 Using drush to setup
migration
 Customizing migration
paths
 Using Features or Drupal
Console or Configuration
Split
 Views upgrades
 Theme upgrades
 Functionality upgrades
 Composer
 All great new things in
Drupal 8
 World Peace
 .... and many more

3. WARNING!
 This demo uses
dev tools
 Things might and
will break
 Interface and
features can
change without
notification
STAY CALM and
DRUPAL ON

5. Website is supporting mission
and operation of your
organization
 Websites are living creatures
 As organization changes, so should
the website
 Websites change, grow, shrink as do
organizations that these sites support
 Website average lifetime is 4-5 years

6. Why do you want to migrate
1. Our organization has changed and
website needs to reflect it
2. We want new fresh feel and look
3. Our site needs to be mobile friendly
4. Our site is very difficult to manage
5. Everyone is on Drupal 8 now
6. Drupal 7 will not have security
updates
WE GOT BUDGET – LET’s BEGIN!

7. What do you want to migrate
 Information architecture
◦ Data models
◦ Relationships
 Content – pages, images, documents
 Designs
◦ Index pages
◦ Pages layout
 Editor’s UX and UI
 Functionality and workflows
 What do you want to keep
 What do you want to delete
 What do you want to change
 What do you want to add

8. READY
FOR
MOVING

9. Using KIPAC website
migration
 Research Center
Website
 Well defined
content types and
relationships
 Good content,
images, video
 Integrated with
mailing lists, etc.
 Non-responsive
theme
 Poor experience
for content
managers

13. Brief history of Drupal migrations
 Upgrades between major
versions of Drupal was a major
undertaking before Drupal 8
 My Drupal migration journey
started with moving 4.7 to D6
 Upgrade in D8 was one of the
most pleasant surprises

14. 4.7 to 5 to 6 - Always an
adventure
Early Migrate module, SQL
scripts

15. 6 to 7 - Routine exercise
Migrate / Feeds Modules

16. 6 to 7 - Routine exercise
 Set up new Drupal 7 site
 Create content types in D7
 Set data export in D6
 Set data import in D7
 Feeds or Migrate
 Unlimited import
 Rollback / Reimport

17. 6/7 to 8
Pleasant walk in the park

18. Two ways to upgrade in Drupal 8
“One-click “ upgrade
via web interface
Configuration >
Development->
/upgrade
Set up migrations via
drush and manage in
Migrations tab
Structure->
Migrations
/admin/structure/migr
ate

19. D8 upgrade
 Set up new Drupal 8 site
 Create content types
 Set data export
 Set data import
 Click Upgrade or run Migrate

20. DEMO

21. Source - D7 site
 Person content
type with various
fields
◦ Text
◦ Date
◦ Entity reference
◦ Image, etc.
 Menu links
 Views

22. Destination - New site D8
 Setup new blank Drupal 8 site
http://dev-siepr-8.pantheonsite.io/
 Lots of modules are now in core (views,
path, etc.)
 Add basic set of modules
1. Admin Toolbar (replaces Admin Menu)
2. Pathauto (requires token and ctools)
3. Devel
4. Ctools
5. Token
6. Diff

23. DevOps
Thanks to Pantheon for providing all
tools
 Dev / test / multidev instances
 Backups
 Db / files export/import
 Drush

24. UPGRADE VIA WEB
INTERFACE
http://dev-drupal-8-content-
migration.pantheonsite.io/upgrade

25. Enable Migration modules
 Core
◦ Migrate
◦ Migrate Drupal
◦ Migrate Drupal UI
◦ Admin menu for convenience of all
operations
◦ Pathauto to ensure migration of aliases if
needed

26. Connect to Source site db
 Db
 User
 Password
 port
 File path

27. List of default migration paths
 ## available upgrade paths
◦ core modules
 ## missing upgrade paths
◦ contrib modules
◦ custom modules
◦ other features
 Continue

28. Demo – Recent Log messages
admin/reports/dblog?page=1

29. Standard upgrade – what
works
 Creates content types / fields even if
there are no nodes of this content type
 Menu items – set in menus, not views
 Moves content – nid’s are preserved
 Url aliases but not pathauto patterns
 Moves users / roles
 Reports every step of upgrade in a log
 Not found or access denied links go to
front page by default

30. Standard upgrade – what does
not work
 One time migration
 Migration rollbacks
◦ Pantheon Backup
 Content for fields is moved, but display
and form display might need to be reset
 Field collections do not have out of the
box upgrade path
 “Plain HTML” format does not work as
expected
 Other issues we are discovering as we
go

31. ENTERS DRUSH

32. Custom updates with drush
 Add modules
◦ Drupal Upgrade
◦ Migrate Tools
◦ Migrate Manifest
◦ Migrate Plus

33. Creating Migration
 drush migrate-upgrade [options] –
config-only (does not move content)
 drush @pantheon.siepr-8.live --
strict=0 migrate-upgrade --legacy-db-
url=mysql://dbusername:dbpasswordh
ere@mysql-user.stanford.edu/dbname

34. Web interface for Migration
 “Execute” button added to web UI in February, get dev
versions here
 https://www.drupal.org/node/2202391/git-
instructions/8.x-4.x/nonmaintainer
 https://www.drupal.org/node/2609548/git-
instructions/8.x-4.x/nonmaintainer
 Migration tab - /admin/structure/migrate
 Migration group -
/admin/structure/migrate/manage/migrate_drupal_7/mig
rations
 Specific migration -
/admin/structure/migrate/manage/migrate_drupal_7/mig
rations/upgrade_d7_node_stanford_person/execute

35. CUSTOMIZING
MIGRATIONS

36. Migrate Manifest
 Standard manifest installed with
Migrate Manifest Module in root
directory /manifest.yml
 Intercept standard upgrade and
launch custom manifest(s)
◦ /manifest2.yml
◦ /manifest-news.yml
◦ /manifest-date.yml

37. Custom migrations
Date format - completed
 Problem: Date format changed
◦ Drupal 7 1994-11-05 08:15:30-05:00
◦ Drupal 8 1994-11-05T08:15:30-05:00
 Solution
◦ manifest-news.yml calls to custom module
(d7_node_stanford_news)
◦ d7_node_stanford_news module includes
configuration for migration
 field_s_new_date:
 Plugin: convert_date
 Source: field_s_news_date
◦ Plugin ConvertDate.php
 Converts date

38. Custom Migrations
Field Format – work in progress
Drupal 7 – text field Drupal 8 – new field

39. Migrations and updates
 One time migration full migration via
Update
 Ongoing updates from Drupal 7 to
Drupal 8 sites via Migrate Plus
 Migration customization using Migrate
Manifest
 Feeds from other sites

40. Current status of Feeds
Module
 .csv import is working
 Tamper UI is ready for review and
approval
 Demo
 Join discussion Feeds weekly meetup
https://drupal.slack.com/messages/C3
4CECZAL/details/ every Thursday 11
am PST


41. Next steps and wish list
 Views upgrade path – some modules
in development
 Integration of Feeds UI with Migrated
back end
 Join discussion at
https://drupal.slack.com/messages/C3
4CECZAL/details/ every Thursday 11
am PST

42. Other very useful modules
1. Webform
2. Display Suite
3. Paragraphs
4. Editor_file