D2L Course Merge

Service Overview

D2L Course Merge allows for the merging of individual course shells within D2L. A course merge requires one of the indicated shells be setup as the destination course. The destination course is where the other shells sections will be merged into. After the merge the enrollments and sections from those shells will exist under the destination course shell.

The use cases for merging a course shell would apply in the below scenarios. 

Scenario A: You teach multiple sections of the same course which results in having more than 1 course shell. You would like to combine these into one single managed course shell that encompasses all sections. 

Scenario B: You teach a section of a course but would like to collaborate with another instructor from another section also teaching the same course and combine shells.  

Scenario C: All sections and instructors of a course would like to collaborate and merge all shells together back into one singular shell containing all sections.

What happens when a course is merged? 

Faculty often teach multiple sections of the same course. In courses that have not been excluded from the individualized course shell configuration this means that an instructor will have a course shell in D2L for each of their sections. A faculty may find it more efficient for their content delivery to merge their sections into one shell versus managing multiple shells. A course merge will accomplish this by taking the enrollments and sections of one offering and combining them into the destination shell. You can then use the filter option in your course to view by section or setup release conditions by semester. Click for Example Diagram

Available To

Faculty

Getting Started

How do I request a course merge?

To request a course merge you can use the "Submit Course Merge" button on this page to submit your request for action. 

Things to note before requesting a D2L Course Merge:

- Course content from the source courses will not be moved to the destination course during the merge process.  The destination courses content will remain unchanged. Your content should be setup post merge or in the destination course ahead of the merge to ensure content efficiency. If you need assistance with accessing/copying course content from a previously offered version of the course or managing content post merge you can email LDSTeam@flemingcollege.ca for assistance 

- Course merge requires that there be no Student data in the course (grades, discussions, assignments) as this data will not be transferable to the destination course.

- The course title will be changed post merge to add an "M" after the section code to indicate it is a merged course.
Example: "CNST 165-S03 Portfolio Development - 2025 Spring" would become "CNST 165-S03-M Portfolio Development - 2025 Spring"

- Course merge requests will only be considered up until day 10 of the semester and only as long as there is no student data present in the shell. Requests outside of day 10 will only be reviewed under extenuating circumstances and if accommodation is possible. 

Can I un-merge my course shells?

If a course merge has occurred and needs to be un-merged a request can be sent in using the "Submit Un-Merge" button on this page.  An un-merge request will only be performed where absolutely necessary and will return the shells to their state before the merge. This will also not be performed if there is student data and is post day 10. 

I need help moving my content from one shell to another

If you need assistance with accessing/copying course content from a previously offered version of the course or managing content post merge you can email LDSTeam@flemingcollege.ca for assistance 

How can I tell if my course has individual course shells in D2L? 

  • If your D2L course shell is an individual course shell, the course code will have a section number in it. For example: CNST 165 is set up with individual course shells for each section and the course code appears as CNST 165-SXX (see image from D2L below). 

    Uploaded Image (Thumbnail)
  • If your D2L course shell continues to be shared (i.e. it is an exception to this new process), the course code will NOT have a section number in it. For example, COMM 202 remains in a shared course shell and the course code in D2L appears as COMM 202 (see image from D2L below). 

    Uploaded Image (Thumbnail)

Additional Information

Course Merge Example Diagram: 

Return to top of page