Migration paths from D7

Created on 13 September 2016, over 8 years ago
Updated 14 July 2023, over 1 year ago

Salesforce Mappings and Mapped Objects need an update / migration path from D7 to D8

πŸ“Œ Task
Status

Active

Version

3.0

Component

salesforce_mapping.module

Created by

πŸ‡ΊπŸ‡ΈUnited States AaronBauman Philadelphia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States maddentim

    Well, it looks like we are going to get serious about this migration soon. I don't think migrating the mapping is critical, but the salesforce_mapping_object and salesforce_mapping_object_revision might be. I am going to start by studying what other modules have done for similar structures.

  • πŸ‡ΊπŸ‡ΈUnited States AaronBauman Philadelphia

    it's been a while since we've done a migration from 7, but if iirc we accomplished this primarily with direct SQL

  • πŸ‡ΊπŸ‡ΈUnited States maddentim

    Thanks Aaron for the response. Looking at the database table structures, I see they are pretty similar. That sounds like a decent path to go.

    Another idea I have thought of would be to just migrate the content type structure and not the data on the Drupal side. From there, we could set up the mapping of the fields that we needed back in Drupal and then pull the data out of Salesforce. So basically, instead of migrating Drupal to Drupal, we migrate from Salesforce to Drupal for this data. .

Production build 0.71.5 2024