Drupal 8 Data Migration Planning

User Accounts Should Be The Same

• Drupal 8 User Account Migration

• If we don’t import the User Accounts from the old website to the new website, then the users will be logging in with different accounts. Is it possible to import users from one instance to another?

• How does the database backend for the Workflow system associate information with User Accounts? If we import user accounts, will this change an internal unique identifier such that the Workflow data no longer lines up correctly with User Accounts?

Date / Times Should Be The Same

• We can’t hand enter this data, as it will have different dates/times.

• Is there a migration tool for this?

• Can we do this with direct SQL?

Workflow Action Notes Should Be The Same

• We should ensure these get brought across to the new website.

• If we can figure out the Date / Times, we should be able to figure out this, right?

If we import the data into the new site, but continue to use the old site for a bit longer, we should also have a plan to keep the audit/decision information synced between the two.

• How can we sync these?

If direct drupal Migration is not an option

• This has proven to be the case, as the Workflow module in D8 is in alpha. The alpha release has all functionality of the original module, however it does not have the migration functionality implemented

• We need to determine possible ways of migrating:

  • The workflows

  • And the data (all the things listed above)

Description

In this option, we have tried a related option that is available on the internet and takes the idea if someone already did migration in order to investigate.

In this option, We have to study internal architecture how the workflow, rule modules module functional in the Drupal 8 sites, and based on those inputs we need to create a custom module that will migrate the data from drupal 7 to drupal 8.

Similar to the option 2, but using direct database calls instead of writing php code to perform the migrations.

In this option, We have to migrate workflow rules from Drupal 8 administrator by taking the reference which we had on the Drupal 7 site.

We will also need to hand migrate the historical Access and Publishing Requests that are contained within the current system. This would be done through the UI interface by replicating original; not by copy the data through the database.

Workflow Rules

Pros

• Time-Saving approach

• Easy to implement

• A custom module can be used on multiple sites.

• Already have some familiarity with the APIs and hooks provided by Drupal 8, which lowers the overhead of research costs

• The IDE will also provide IntelliSense when working with objects provided by the modular creator (lowers research costs)

• Time-Saving approach

• Easy to implement

Cons

• Very less information available and haven't found any successful workaround regarding the same.

• Time-consuming approach

• The Workflow modules specific APIs and hooks need to be researched and tested

• Time-consuming approach

• We will have to also understand if there were any value/data definition changes within the new database to correctly apply the transformations.

• Workflow states and rules condition should be accurate. otherwise, functionality will not work as excepted.

Data

• Drupal site is having 2 workflows i.e “API Publish” and “Application Approval Request” which will have their certain state respectively.

• Workflow Rule is having 14 rules based on a certain event condition.

• Drupal site is having 2 workflows i.e “API Publish” and “Application Approval Request” which will have their certain state respectively.

• Workflow Rule is having 14 rules based on a certain event condition.

• Drupal site is having 2 workflows i.e “API Publish” and “Application Approval Request” which will have their certain state respectively.

• Workflow Rule is having 14 rules based on a certain event condition.

Pros

• Already have some familiarity with the APIs and hooks provided by Drupal 8, which lowers the overhead of research costs

• The data storage logic has already been written by the module owner, so we won’t make mistakes by going this approach (lower risk)

• The IDE will also provide IntelliSense when working with objects provided by the modular creator (lowers research costs)

Cons

• We will need to research the difference between the D7 and D8 database schemas.

• We will have to also understand if there were any value/data definition changes within the new database to correctly apply the transformations.

• Reproducing the accurate Dates and Times of the original approvals (who they were done by and when) could not be replicated in this approach. (There would be data loss, or data distortion.)

Notes

On the basis of research on the internet, there is no direct way available to migrate workflow and rules directly from Drupal 7 to Drupal 8.
Here is the list of the POC:-
1: I have tried migration through the Drush commands. These steps are given in the doc Migration Process from Drupal 7 to 8

Result: Failed, I have tried to migrate workflow and rules data through the brush but the process is not supported to migrate the data from D7 to D8.

Useful Link: https://www.drupal.org/docs/upgrading-drupal/upgrade-using-drush

2: Tried to import workflow state by adding code and followed steps mentioned here in this link https://www.drupal.org/docs/upgrading-drupal/upgrade-using-drush But there is not success found with that.

Result: Failed, As node was not imported to the D8.

3: In order to migrate rule from D7 to D8, I have used a few modules with providing missing functionality in Drupal 8. Here is the list of those modules.

• D8 Rule Essentials

• Typed Data

Result: Failed