Choosing an LMS in Iraq: Data Export and Content Ownership Questions

Three years after signing, an Iraqi company decides to replace its LMS software. The learning team asks the LMS software provider for its data and receives a spreadsheet of course completions. There are no course versions, no attempt history, and no record of who corrected results by hand. The certificates arrive as images. The twenty Arabic courses the provider built for the company cannot be handed over in editable form, because the contract never mentioned source files.

None of this was hidden. Nobody asked. During selection, everyone focused on what the LMS software could do on day one, and nobody tested what would happen on the last day.

This article gives HR, IT and procurement teams in Iraq a practical way to ask those questions before contracting: an exit test you can run while trialling LMS software, a list of training records that must leave with you, and content ownership questions to settle for each type of course. It is not legal advice. Who owns a course, and what you may do with it after the contract ends, depends on the contract and the applicable law, so involve your legal adviser before you sign any LMS software agreement.

Why LMS Software Exit Questions Belong Before You Sign

UK government guidance on managing technical lock-in in the cloud describes lock-in as the situation where switching from one technology or provider to another is difficult, time-consuming, and disproportionately expensive. It notes that long and inflexible contracts can prevent organizations from changing their strategy, and that for software delivered as a service, choosing products that use open standards and formats keeps you in control of your data.

That guidance is written for the UK public sector, not for Iraqi companies, but the logic transfers directly to LMS software and other learning management solutions, where vendor lock-in builds up quietly. Your bargaining position is strongest before signature. Once training records, courses and user habits have built up on one platform, every exit question becomes harder to raise and more expensive to resolve. The same guidance also reminds public bodies to retain ownership of, and access to, data held by third parties, a principle worth adopting whatever your sector.

The Exit Test: Leave the LMS Software Before You Join

An exit test is a rehearsal of leaving your learning management software. During the trial or pilot, load the LMS software with realistic test data, then ask for a full export exactly as you would at the end of the contract. Prepare the test data so it covers the cases that usually cause trouble:

• Users with Arabic names, including names that also appear in Kurdish or English spellings.

• Courses with two versions, so you can see whether completions stay linked to the right version.

• Completions, failed attempts, retakes, and a manually corrected score.

• Certificates with expiry dates, and one uploaded certificate from external training.

• A classroom session recorded by a supervisor, with attendance and a sign-off.

Then check the export as if you were the next LMS software provider receiving it. Do the files open without corrupted Arabic text? Is every user identified by a stable employee number rather than a name? Do the files keep the links between users, courses, versions, and attempts, or do they flatten everything into one summary sheet? Are uploaded documents and certificates included as files? And how long did the export take, who had to be involved, and could your own administrator run it without opening a support request?

Ask the LMS software provider to write down what the test export left out, and whether the full export at exit would differ. An honest gap list at this stage is worth more than a verbal assurance that ‘everything can be exported’.

Training Records That Must Leave the LMS Software with You

A completion list is not a training history. Agree on a field list with your HR and audit teams and attach it to the evaluation of each LMS software option. At a minimum, it usually covers:

• User profiles with employee number, department, branch or site, and status.

• The course catalog with version numbers and publication dates.

• Assignments and due dates, including who assigned them and by which rule.

• Completions, scores, attempts, and timestamps.

• Certificates, their issue and expiry dates, and external training records.

• Manager sign-offs, observation checklists, and uploaded evidence.

• The audit trail of manual changes to any record.

Ask in which formats each item can be exported, and prefer open, documented formats over a proprietary backup file that only the same LMS software can read. If the platform stores detailed learning activity as statements under the xAPI specification, which describes communication about learner activity and experiences between technologies, ask for a sample export of those statements as well as the summary reports.

Ask too what happens to your data after the LMS software contract ends: how long the provider keeps it, how and when it is deleted, whether backups are included, and what written confirmation you receive. Receiving the export is only half of an exit. Loading it into a new system is the other half, and our guide to migrating training records to a new LMS covers that later stage.

Content Ownership: Questions to Settle by Content Type

Content ownership is where misunderstandings are most expensive, because ‘our courses’ can mean several different things. Separate your content into types and ask every LMS software provider the same questions about each one:

• Content you upload: files, videos, and documents your own staff created. Confirm that the contract does not give the provider rights beyond hosting them, and that you can download them in their original form.

• Custom content built for you: courses the provider or its partners develop to your specification. Ask who owns them, whether you receive the source files as well as the published package, and whether you may edit and reuse them with other LMS software.

• Licensed content: ready-made library courses included in an LMS software subscription. Expect access to end with the contract, and ask whether completion records for those courses remain yours.

• Templates, players and themes: the provider’s own tools that wrap your content. Ask whether your courses still work outside that LMS software.

• Arabic or Kurdish adaptations and recorded sessions: translations, voice-overs and session recordings made during the contract. Ask who holds the rights and in what format you receive them.

Source files deserve particular attention. A published course package lets you run a course; the editable project files, video masters and text files let you update it when a procedure changes. If the contract is silent, do not assume either way. Put the questions to your legal adviser, and record the agreed answer for each content type. For the practical side of moving a library later, see our guide to migrating a course library to a new LMS.

Writing Exit Terms into the LMS Software Contract

Your legal team will choose the wording, but procurement and IT can make sure the commitments are practical and testable. Before signing, agree in writing:

• An annex listing the export fields and formats, based on your exit test.

• An exit assistance period during which the LMS software stays available and the provider helps with the export, and whether that assistance is included or charged separately.

• A content handover list stating, for each content type, what you receive and in which format.

• Deletion of your data after a confirmed export, with written confirmation.

• A repeat of the exit test after major upgrades, so the export does not quietly degrade.

If your sector also has strict rules on who may see training records, combine these terms with the access requirements discussed in our article on tracking and access requirements for Iraqi banks.

A Hypothetical Example: Comparing Two LMS Software Offers in Basra

The following example is hypothetical and only illustrates the method.

An engineering services company with sites in Basra and Erbil has shortlisted two LMS software offers for its safety and technical training. Both demos went well. Before deciding, the learning team runs the same exit test on each LMS software trial, using forty test users and six test courses.

The first provider’s export arrives within a day, but Arabic names appear as question marks, attempt history is missing, and manual corrections are not recorded anywhere. The second provider’s export is complete and readable, but its proposal states that custom courses remain the provider’s property and that only published packages are delivered at exit.

The company does not treat either result as a final verdict. It asks the first provider to fix the export and repeat the test, and asks its legal adviser to negotiate source-file delivery with the second. The second provider agrees to deliver editable files for courses built from the company’s own procedures, while its library templates stay excluded. The company signs with that LMS software, and the exit test results and content handover list become annexes to the contract.

Summary

The easiest time to answer LMS software exit questions is before you need them. An exit test during the trial shows what your data really looks like when it leaves, a field list defines which training records must travel with you, and content ownership questions by type prevent the most expensive surprises.

Treat the answers as part of choosing LMS software, not as paperwork for later. Settle ownership with your legal adviser, write the practical commitments into the contract, and repeat the exit test after major upgrades so the way out stays open.

Click here. If you are preparing exit and ownership questions for an LMS software shortlist, you can discuss your requirements with the SkillUp MENA team.