![]() ![]() ![]() If you have received some or all of your content in the XML, CSV, or other text-type formats, you may just have to open the files and read them to see what you are working with. If your source data is not in a content management system (or you don’t have access to it), you may have to dig into the database directly. Note that author is often a reference to users, so you’ll need to consider migration order as well. You should give some thought to how you will map those fields across as well. Most CMS systems will also have a set of meta-data that is pretty similar to Drupal’s: created, changed, author, status and so on. Does your source site allow comments? That maps pretty closely to Drupal comments, but make sure that you actually want to migrate them before putting in the work! Drupal 8 Content Migration: A Guide For Marketers, one of the early posts in this series, can help you make that decision. Are Editors and Writers stored in two different database tables? Well, you probably just discovered two different user roles, and will be putting both user types into Drupal users, but with different roles. Is there only one ‘content type’, which is differentiated by some sort of tag (“Blog Post”, “Product Page”, etc.)? Well, then, each of those might be a different content type in Drupal. So, the first part of your job is to figure out how all that works. And it’s almost certain to have some sort of user account. Most content management systems have at least some structure that is similar to Drupal’s node types, as well as a tag/classification/category system that is analogous to Drupal’s taxonomy. But what do you do if you are moving to Drupal from another system? Well, you will need to do a little extra analysis in your discovery phase, but it’s very doable. One of the first steps of a Drupal to Drupal migration is setting up the content types in the destination site. We’ll be building on some of those concepts here. If you haven’t read through the previous installments, I highly recommend you do so. This post, though, will cover what you do when your content is in some other data framework. So far, readers of this series will have gotten lots of good process information, and learned how to move a Drupal 6 or 7 site into Drupal 8. Drupal 8 Migrations: Taxonomy and Nodes - Migrate the bulk of Drupal content and classifications.Managing Your Drupal 8 Migration - Key concepts, setting up the tools, and starting with a user migration.The Top 5 Myths of Content Migration - Mistaken ideas, traps, gotchas, and mismanaged expectations.Estimating Drupal 8 Migration Scope - How long will all this take?.Drupal 8 Content Migration: A Guide For Marketers - What content should we migrate, and how do we organize and plan a migration?.We’ve already covered some important migration information on our blog: Content migration is a topic with a lot of facets. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |