Export data from Blackboard before your contract changes
Export your course packages and archives while your Blackboard contract is still active, because those files are the only complete copy of course structure, submissions and grades you can take with you. Blackboard Learn produces course export packages for course content and archive packages that carry more of the course record, including submissions, grades and attendance where your institution uses those features. Confirm with your Blackboard administrator which export and archive options are enabled in your version, who holds the system-level permissions to run them, and where your institution stores the files once they are downloaded. Start this inventory early. Renewal dates, hosting changes and data residency reviews all tend to arrive with less notice than the export itself needs.
Plan for three limits. First, archive packages expire after 30 days, so download each package as soon as it finishes and move it to storage you control. Second, a Common Cartridge export moves content into another system but leaves out grading, random question blocks and discussion threads, so those records need their own export or a documented manual copy. Third, some data may sit outside any package, such as LTI tool records, roster links to your student information system and custom gradebook schemes. Ask your Blackboard administrator to list each of these, and record which one you will capture and how. A short table of course, data type, export path and owner makes the gaps visible before the contract date.
Keep the scope to documented export paths. The sibling pages on migrating to Moodle and to self-hosted Canvas LMS cover how those packages are imported, rebuilt and reconnected, including the Canvas Course Import Tool's support for Blackboard 6 through 9 and Ultra exports. Blackboard's self-hosted release history is also relevant to timing. Managed hosting has not been supported since December 31, 2022, and the latest self-hosted Learn release listed is v3900.84.0 from February 15, 2024, so check your release against the Blackboard release schedule and ask your vendor to confirm the export options that apply to your installation before you rely on them.
What Blackboard Learn exports, by format and method
This table lists each data type you may need from Blackboard Learn, the export method and file format that carries it, and the limits you must confirm before planning a migration. Read each row against your own export settings, because archive contents and expiry depend on your administrator configuration and Blackboard version.
| Data type | Export method | Format | Limits or notes |
|---|---|---|---|
| Course export package | Course export from the course management area | Blackboard course package | Carries course content and structure. Confirm the package expiry window in Blackboard's administrator documentation for your version. |
| Course archive package | Course archive by an administrator or instructor, depending on permissions | Blackboard archive package | Adds student records to the course content. Confirm the 30-day package expiry for your version before scheduling exports. |
| Submissions | Included in archive packages when selected | Archive package contents | Student files and attempts are available only where the archive includes them. Confirm whether your settings capture all submission types. |
| Grades | Included in archive packages when selected | Archive package contents | Gradebook data may not map one-to-one to another LMS. Plan to verify grade totals and weighting after import. |
| Attendance | Included in archive packages when selected | Archive package contents | Confirm with your Blackboard administrator that attendance data is part of the archive for your deployment and whether it can be read by the target system. |
| Course content and files | Course export or archive package | Blackboard package with embedded files | Files and links travel with the package. Check external links and embedded media after import, since they may point to Blackboard URLs. |
| Common Cartridge | Common Cartridge export, where offered in your version | IMSCC or Common Cartridge ZIP | Canvas's Course Import Tool reads Common Cartridge ZIP and IMSCC files. Confirm with Moodle import documentation for your target version that it reads this format, and expect omitted items such as grading and some quiz structures. |
| Thin Common Cartridge | Common Cartridge export variant | Thin Common Cartridge file | Canvas can import Thin Common Cartridge files as module content. Confirm equivalent handling in Moodle before relying on it. |
What an archive adds beyond a course export
A course export carries the course structure and materials, but an archive package is the record you keep when the learner-level history matters. Before you choose an export type, confirm in your own Blackboard Learn version exactly which records each archive includes, because the answer varies with configuration and version. Ask your Blackboard administrator to check whether the archive contains student submissions, grades and attendance records, and whether those records are present for every course in scope or only for selected ones. Write the answer down with the date you checked it, since it becomes part of your retention evidence.
These records matter because registrars, accreditation reviewers and internal auditors often need to show what a learner submitted, what grade was recorded and when attendance was taken, sometimes years after the course closed. Rebuilding that history in a new LMS is rarely a faithful substitute. Grades recalculated from migrated settings, resubmitted files and re-entered attendance can differ from the original record, and the new system will carry its own timestamps. For that reason, most institutions hold archive packages as stored files under their records retention schedule, with access control and a documented owner, and only bring forward the data they actively teach from. Confirm the retention period, the storage location and who may restore an archive before the Blackboard tenant is switched off.
What does not come out cleanly, and the workaround for each
A Common Cartridge or standard course export carries content but not every kind of course data. The items below are the ones most likely to need a separate export, a records archive or a manual rebuild in the target LMS. Confirm each one against your own export before you plan the cutover.
Gradebook structure and calculations
Common Cartridge carries course content, not the live gradebook. Column weights, calculated totals, drop rules and grading schemes usually have to be rebuilt in the target LMS from a results export. Export grades to a spreadsheet or archive, then compare totals for a sample of students before you close the old course. Check the calculated columns first, because they are the easiest values to lose silently.
Random question blocks
Question pools that draw a random set of items per student are logic in the assessment, not a static question list. A flat content export may keep the questions but lose the rule that selects them, so each student could see a different or incomplete quiz. Recreate the question bank and selection rules in the target quiz engine, then test with a few sample student attempts. Keep the original quiz results in the archive for records.
Discussion threads and replies
Discussion boards are usually exported as forum structure with prompts, while student posts, replies and grading threads may not carry over. Learners' contributions are part of the academic record, so keep a read-only export or archive of threads that you must retain. If the target course needs live discussions, reopen new threads and state clearly which history is archived rather than migrated.
LTI tool connections
External tools such as publishers' content, plagiarism checkers and proctoring services are connected through LTI registrations, keys and launch URLs. These connections are tied to the source platform and do not move with the course files. Inventory every tool in use, request new credentials from each vendor for the target LMS, and reconfigure the placements in each course. Test a launch and a grade passback for each tool.
SIS link and enrollment data
Course rosters, section codes and grade return to the student information system depend on integration settings and identifiers that live outside the course package. A content export does not rebuild these links. Document the current SIS feed, map section and user identifiers, and run a test term or sandbox sync before the first live term. Confirm who owns the SIS integration on both sides.
Embedded third-party content
Videos, interactive modules and library items that are embedded through vendor players or hosted content may appear as broken links after import, or may need a license check before they are moved. Inventory embedded resources by course, confirm which the vendor still licenses for your new platform, and re-embed or re-upload the approved ones. Remove any link that depends on the old Blackboard domain.
The sequence for a complete export and verification
This sequence moves every course, archive and record out of Blackboard in an order that protects the export windows, and ends with packages you can open, check and retain. Each step leaves a written output that the next step depends on.
Inventory courses and record owners
Build a list of every course, organization and archive you need to keep, with the instructor or administrator who owns each one, the term it ran in and whether it holds student submissions or grades. Ask your Blackboard administrator to confirm which courses are active, which are already archived and which are scheduled for retirement. Done when every item on the list has a named owner and a status, and someone outside the course team has reviewed it for completeness.
Confirm the Blackboard version and export paths
Identify which Blackboard product and version your institution runs, whether that is Learn with the Original course view, Learn with the Ultra experience, or another deployment, and check which export types that version offers in its documentation. Confirm whether course exports, archives with student data and Common Cartridge exports are available to your role, and note any limits that apply. Done when you have a written list of the export types you will use for each course category, approved by the administrator who holds the Blackboard export permissions.
Run course exports and archives early
Start the exports for the courses with the longest dependency chains first, and run archive packages for any course that holds submissions, grades or attendance records. Confirm the package expiry window in your Blackboard documentation before you begin, because packages can expire and must be downloaded in time. Done when each package has been generated, downloaded and logged with its course ID, export type and date, and no package sits unclaimed past its window.
Store packages with checksums and a manifest
Place every downloaded package in a controlled storage location with access limited to the records and migration team. Generate a SHA-256 checksum for each file and write a manifest that lists the file name, course ID, export type, checksum and the person who exported it. Done when the manifest and checksums are stored separately from the packages, and a second person has confirmed that the checksums match the files.
Verify content by opening packages
Open a sample of packages from each export type in a test environment, then compare item counts for content, discussions, assignments, quizzes and files against the source course. Record any differences, such as missing attachments, unsupported question types or content the export does not carry, and tell the reader which items need manual rebuilding. Done when each sampled package has a verification note that lists counts, known gaps and the reviewer's name, and any gap that affects records has an agreed owner.
Export records for retention
Export grade reports, submission histories, attendance data and enrollment records as separate files in formats your records team can read without Blackboard. Compare the record totals with the archive packages for the same courses, and confirm with your records or compliance owner which retention rules apply to each record type. Done when the records files, their checksums and the reconciliation notes are added to the manifest and the records owner has signed off on what is kept and where it is stored.
Where the exported content goes and what the target needs
Moodle is the most common target for courses leaving Blackboard, but it does not import Blackboard Learn archives directly, so the export is rebuilt into Moodle through Common Cartridge or manual course building. Readiness depends on the release line you choose, because each one sets its own PHP and database floor and its own upgrade rule.
- Release lines: Moodle 4.5 is a long-term support release from 7 October 2024 with security support until 4 October 2027. Moodle 5.3, released on 5 October 2026, is the next LTS with general support until 4 October 2027 and security support until 1 October 2029.
- Version requirements: Moodle 5.1 needs 64-bit PHP 8.2 or later and PostgreSQL 15, MySQL 8.4, MariaDB 10.11 or SQL Server 2017 or later. Moodle 5.3 needs 64-bit PHP 8.3 or later, PostgreSQL 17, MySQL 8.4, MariaDB 11.4 or SQL Server 2019 or later.
- Upgrade path: Sites must already run Moodle 4.2.3 or later to move to 5.1, and Moodle 4.4 or later to move to 5.3.
- Web root: From Moodle 5.1, the web server document root must point to the
/publicdirectory, not the main Moodle folder, or the site may show directory listings or errors.
Confirm the version requirements at the time of planning, because the release schedule and minimum versions can change between now and your cutover.
Canvas LMS is the target with the most direct import path from Blackboard. Its Course Import Tool reads Blackboard 6, 7, 8, 9 and Ultra exports, and it also reads Common Cartridge ZIP or IMSCC files. Thin Common Cartridge files can be imported as module content. Canvas code is AGPLv3, so you can run it in your own infrastructure.
- Blackboard imports: The importer accepts Blackboard 6 through 9 and Ultra exports, so confirm which version produced your export before you start.
- Common Cartridge fallback: If the Blackboard import does not map a content type you need, a Common Cartridge file is an alternate route, and Thin Common Cartridge files bring in module content.
- Manual rebuild: Gradebook structure, assessment settings and integrations usually need checking and rebuilding after import, so plan time for that review.
- Support model: Self-hosted Canvas is supported by the community, so your team or a partner carries patching, backups and upgrades.
Run a test import of one representative course into a non-production Canvas instance and compare the result with the original before you schedule the full migration.
Some records, such as completed course archives with submissions, grades and attendance, must be kept for retention even when the course does not move to a live LMS. An archive store holds those packages as files rather than as running courses. The requirements come from your records policy, not from the LMS.
- Retention: Set the retention period from your records schedule and legal hold rules, and record who approves disposal. Do not rely on the 30-day package expiry as a retention control.
- Access control: Limit read access to records staff and auditors, and log access to student data. Use your existing identity provider so access ends when staff leave.
- Format: Keep the original Blackboard package unchanged, and store a copy of the exported spreadsheets or reports in an open format such as CSV or PDF/A so they can be read without the LMS.
- Integrity: Store checksums with each package and keep them on write-once or versioned storage where your policy requires it.
- Encryption: Encrypt archives at rest, and keep the keys separate from the files.
Confirm with your records manager and legal team which fields and formats must be preserved before you choose the storage tool.
What to plan before renewal or termination
Blackboard export work tends to start late, when the contract end is already close. The decisions below set the order of work: confirm the export path, test it early, and secure the records you must keep. Each one shapes whether your archive is usable after the subscription ends.
Export deadline and package expiry
Find out how long a generated course export or archive package stays downloadable. Exports from Blackboard are not kept indefinitely, so a package generated the week before termination may already be gone when you need it. Build a calendar that works backward from the end date, and schedule each export with time to download, check and store the file. Confirm the expiry window with your vendor in writing, since it governs how many export rounds you can afford.
Data ownership and written export requests
Confirm in your contract who owns course content, student submissions, grades and attendance records, and what the vendor must return at exit. Ask for the vendor's written export procedure and any export fees before you rely on it. Send formal requests by email or ticket so you have a dated record of what was asked and what was delivered.
Test export before the notice date
Run a full test export of one representative course, including one with archives, before the notice deadline. Import that package into a sandbox of your target platform and check that content, files, links and question banks survive. The results tell you what must be exported manually and how long the full migration will take, so you can decide whether to give notice on time.
Retention obligations for submissions and grades
Identify which records your institution or employer must keep, such as graded submissions, final grades and attendance, and for how long. Archives can carry this student data, so decide who can access it, where it is stored and how it is deleted at the end of the retention period. Involve your records office and privacy officer before the export runs, not after.
Target platform readiness window
Schedule the replacement platform's build, configuration, integration and test work so it finishes before the Blackboard access ends. For self-hosted Moodle, check the PHP and database versions the release requires and plan the server setup in advance. Keep at least one full cycle for user acceptance testing with instructors, because content problems often appear only when real courses are used.
Archive access after the subscription ends
Decide how you will read archived courses, submissions and grades once the subscription closes. Export files in standard formats, store them in a system you control, and confirm that someone on your team can open and search them without a vendor login. Document the storage location, access roles and the person responsible for the archive.
Questions buyers ask before exporting from Blackboard
How long does a complete Blackboard export take?
No supplied source gives a duration for a full Blackboard export, so confirm it with Blackboard and in a pilot run against your own data. The effort is driven by course count, the volume of embedded media and attachments, whether you include course archives with student submissions and grades, and how many LTI tools and external links hold content outside the course. A pilot of a representative set of courses shows the real pace and exposes problems before you commit to a full schedule. Ask your team to time each stage: export, download, validation and import into the target system.
Can our own team run the export without outside help?
Often yes for a small set of standard courses, because the export is a built-in administrator function. The harder part is the surrounding work: deciding what to keep, checking that packages download and open, and mapping content that Common Cartridge does not carry. Teams without Blackboard administration experience, or with large archives containing student records, usually benefit from a fixed-scope engagement that agrees deliverables in writing before work starts. DeployOpen plans and runs this kind of export and validation work in the client's own infrastructure under a written scope.
What do administrators and instructors need to provide?
Administrators own the export permissions, the storage location, the retention decision and access to the Blackboard environment. Instructors confirm which courses are still active, which materials are current, and which assessments, question banks and discussion threads must survive the move. Both groups should sign off on a course inventory before exports start. Without that sign-off, teams often export courses that should have been archived and miss content that exists only in one instructor's workspace.
What should we ask Blackboard to confirm in writing?
Ask Blackboard, in writing, which export formats your deployment supports, the expiry period for generated packages, how long archives remain downloadable, and whether any export function is limited for your hosting model. Also ask for the supported Learn release on your side, because the supplied release information shows that managed hosting is no longer supported and that the latest self-hosted release listed is v3900.84.0 from February 15, 2024. Check the Blackboard release schedule and confirm current status directly with your account team.
What happens to submissions, grades and attendance during export?
Standard course exports and Common Cartridge packages carry course content, not the full learner record. Course archive packages can include student submissions, grades and attendance data, which makes them the main route for records retention, but they also contain personal data that needs access controls and a defined retention period. Confirm with Blackboard exactly which data each package type includes, and plan a separate export of gradebook data in a readable format if your target system must show historical grades.
Can the gaps in Common Cartridge export be closed?
Yes, in most cases, but the work is manual or needs custom tooling. Common Cartridge does not carry everything, so items such as gradebook settings, random question blocks and discussion threads need to be documented and rebuilt or mapped in the target LMS. Inventory these items per course, decide which can be rebuilt by hand, and script the rest where the volume justifies it. Confirm each gap against your own export files, since the exact coverage depends on your course types and tools.
Which cost drivers should we include in a quote?
The main cost drivers are course count, media volume, archive scope, the number of LTI tools and integrations to reconnect, and records retention requirements. One-time costs cover inventory, export runs, validation, mapping and rebuilding; recurring costs cover storage for retained archives and access management. When requesting a quote, ask for a fixed-scope statement listing included courses, archive types, LTI tools, validation steps and handover documents. No supplied source gives prices for Blackboard exports, so compare quotes against this written scope rather than against an estimate.
How DeployOpen scopes and delivers a Blackboard data export
DeployOpen treats a Blackboard export as a scoped engagement, not a one-click task. We agree in writing which course packages, archives and student records are in scope, then build, verify and document the export inside your own environment so the output can be reviewed by your registrar, compliance team and migration target.
How we scope
- Inventory which courses, terms and archive packages must leave Blackboard Learn, and which can be retired
- Confirm whether archives with submissions, grades and attendance are required for records retention
- Agree the target platform, such as Moodle or self-hosted Canvas LMS, before choosing the export format
- Document who approves the written scope, deliverables and timeline before any work starts
How we build
- Run course exports and archive packages from a test copy first, checking for the 30-day package expiry window
- Map what Common Cartridge output omits, such as grading, random question blocks and discussion threads
- Store exports and student data in your own storage, with access limited to named staff
- Test a sample course import into the target platform and record every item that needs manual rebuilding
How we hand over
- Deliver an export log listing each package, its date, its contents and its location
- Provide a gap register covering grades, quizzes, LTI tools and SIS links that were not carried over
- Document the steps so your own team can repeat the export for remaining courses
- Hand over copies with agreed retention controls so evidence for audits can be produced later
How we support
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing first
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- Ask any quote to itemize the export, verification, documentation and support effort separately
- Confirm with your Blackboard administrator which packages are still downloadable before scoping starts
