Common pitfalls and how to avoid them

Each of these has happened to us. The agent knows them, and the tool checks for the ones marked checked.

  1. Exporting without course files. You get an outline and no content. Tick “Include course files” on the last screen.
  2. One stray quotation mark. A single unescaped " in a file made D2L refuse a 669 MB package with only “Conversion failed.” Checked: the tool will not build a package with a broken file.
  3. Re-importing a quiz. D2L makes a second quiz and does not update the first. A quiz with attempts can only be repaired by hand. Import into a new, empty shell.
  4. Importing Grades into a shell that has grade items. Items match by exact name, so a one-character difference makes a second column. Leave Grades unticked when the shell already has a gradebook.
  5. Pictures embedded in a quiz. D2L breaks them on import and students see a broken image. Use image files. Checked.
  6. Dates in page text, Word files and slides. The date shift moves stored dates only. Checked: the quality report lists pages with dates in their text.
  7. Typing the academic calendar from memory. Finals were a week off in three of our courses once. Look it up and confirm it.
  8. Renaming a graded item. The new name matches nothing in the gradebook and makes a second column. Name quizzes for what they cover, not “Quiz 7.”
  9. Instructor-only material left visible. Hidden does not always mean left out of the package. Checked for obvious names such as “answer key.”
  10. Deleting instead of removing. Deleting a quiz deletes its attempts, and deleting an assignment folder deletes its submissions. Use “Remove from Content” in a shell with students.
  11. Recreating an outside-tool link. It will not be paired and will not return grades. Move the existing one.
  12. Trusting a clean package. A package can report zero broken links and still be missing most of its graded work. Checked: the report lists gradebook items with nothing behind them.

Last checked 2026-11-12.