As we approach this weekend’s Unit Offer Unification release, we wanted to provide you with a clear overview of what to expect immediately after release and what actions are required from your team.
Following the release, your existing Units of Study, enrolments, and TCSI related data will be migrated into the new structure through our Migration Script.
The purpose of this migration is to ensure that your existing data remains available and operational within the new Unit Offer model.
What you may notice after release
As part of the migration:
- Units of Study will now appear as Units with the new Unit Of Study flag enabled
- New Unit Offers will be created for migrated Units of Study
- Existing Unit of Study enrolments will now appear as Unit Enrolments linked to the related new Unit Offers and Units
- Unit Offer hierarchies will be used to represent relationships between Units of Study and related Unit of Competencies
For most customers, the migrated structure will be fully usable immediately following release.
However, some customers may notice duplicate or similar Units of Study appearing at the Scope > Units level.
For example:
| Type | Unit Code | Unit Description | Unit of Study Flag |
| Existing Unit | ACC101 | Accounting Fundamentals | False |
| Migrated Unit of Study | ACC101 | Accounting Fundamentals | True |
This is expected.
The migration creates one Unit for each Unit of Study code and description found in the previous structure. Where different Course Offers used slightly different Unit of Study codes or descriptions, multiple Scope-level Units may be created.
For example:
| Type | Unit Code | Unit Description | Unit of Study Flag |
| Migrated Unit of Study | UoS12024 | Unit of Study 1 2024 | True |
| Migrated Unit of Study | UoS12025 | Unit of Study 1 2025 | True |
| Migrated Unit of Study | UoS12026 | Unit of Study 1 2026 | True |
This does not impact enrolments, delivery, reporting, or TCSI compliance.
Understanding the next phase: Unit of Study Scope Merge Process
After you have had an opportunity to review your migrated data, Wisenet will provide a one-time Unit of Study Scope Merge Process.
The purpose of this process is to help create a cleaner Scope-level Unit structure by consolidating duplicate or similar Units of Study records.
It is important to understand that this process:
- Only affects Scope-level Unit records
- Does not change Unit Offer codes or descriptions
- Does not change enrolment data, delivery structures or TCSI reporting values
The goal is simply to establish a cleaner and more maintainable Unit of Study structure at the Scope level going forward.
How the merge process will work
Step 1: Run Report #9025 – Unit of Study Review Report
Run the report #9025 Unit of Study review report and download raw data to excel.
The report will return Units where UnitOfStudy = True, sorted by UnitCode to make it easier to identify similar or duplicate records.
The report will include:
- UnitId
- Unit Code
- Unit Description
- Organisational Unit Code
- Field Of Education
- Year Long Indicator
- CourseId, using the maximum value where relevant
- Course Code
- Course Description
- Unit Offer Count
- New Unit Code
- New Unit Description
Step 2: Review and nominate the clean Scope-level structure
Review the exported spreadsheet and determine the Scope-level Unit of Study structure you would like to retain moving forward.
Use the New Unit Code and New Unit Description columns to nominate the preferred Scope-level Unit of Study values.
Where multiple Units represent the same Unit of Study, enter the same New Unit Code and New Unit Description for those records to indicate they should be consolidated into a single Scope-level Unit.
For example:
| Unit Code | Unit Description | New Unit Code | New Unit Description |
| UoS12024 | Unit of Study 1 2024 | UoS1 | Unit of Study 1 |
| UoS12025 | Unit of Study 1 2025 | UoS1 | Unit of Study 1 |
| UoS12026 | Unit of Study 1 2026 | UoS1 | Unit of Study 1 |
Important: This process only consolidates Unit records at the Scope level and does not affect Unit Offers, enrolments, delivery structures, or TCSI reporting data.
Step 3: Submit the Completed Spreadsheet to Wisenet
Once your review is complete, submit a support ticket with a subject – Unit of Study Scope Merge Process and attach the completed spreadsheet.
The support ticket confirms that you have reviewed the proposed Scope-level Unit codes and descriptions and are ready for Wisenet to validate the file.
Step 4: Wisenet Reviews and Validates the File
Before any changes are made, Wisenet will review and validate the submitted spreadsheet.
Validation checks will include:
- Missing New Unit Code or New Unit Description values
- Unit records that cannot be matched
- Validation that all related Unit Offers can be mapped correctly to the nominated Unit
Once validation is complete, Wisenet will generate a pre-validation report showing the proposed changes.
No merge activity will occur during this stage.
Step 5: Review and Confirm Proposed Changes
Review the provided pre-validation report.
This report will show:
- Which Units will be merged
- Which Unit will be retained or created
- The final Unit Code
- The final Unit Description
- Which Unit Offers will be mapped to the retained Unit
- Any excluded records
- Any validation issues requiring review
Please review the proposed changes carefully. The merge process will only proceed once written confirmation has been received in the support ticket.
Step 6: Wisenet Runs the Merge Units Script and provides confirmation
Once the merge process has been completed, Wisenet will provide confirmation through the support ticket.
Where appropriate, a post-merge report may also be provided showing:
- The final Scope-level Unit of Study records
- Unit Offers mapped to each Unit
- Any records that could not be merged
- Recommended post-merge validation activities
What happens after merge
The Unit of Study Scope Merge Process is designed to help establish a cleaner and more maintainable Scope-level Unit structure following migration.
For many providers, the merge process will be sufficient to achieve their desired long-term structure.
Where additional consolidation or clean-up is required, Wisenet can work with you to review and simplify Unit Offers and related Unit Enrolment records as appropriate for your organisation.
As every provider’s setup is unique, we will work with you to determine the most suitable long-term structure while preserving offers, enrolment and compliance requirements.
Looking Ahead
While there will be some adjustments as you become familiar with the new structure, these changes represent an important step forward in simplifying how Units of Study are managed within Wisenet.
The new model creates a stronger foundation for future enhancements, including improved enrolment management, better integration with delivery workflows, expanded bulk update capabilities, and a more consistent experience across Units, Unit Offers, and Unit Enrolments.
If you haven’t yet had the opportunity to explore the upcoming changes, we encourage you to watch the Unit Offer Unification webinar recording and also read the Unit Offer Unification announcement.
As always, our team will continue to provide guidance, resources, and support throughout the transition. We appreciate your partnership as we deliver these improvements and look forward to helping you make the most of the new capabilities available in Wisenet.