Important Update
Audience: LMS administrators, academic technology leaders, instructional designers, information security teams, and IT teams
Products Impacted: EchoVideo, EchoPoll, EchoExam, PointSolutions, GoReact
Summary
The education technology industry is accelerating its transition away from legacy LMS integrations as institutions, LMS providers, and technology vendors adopt stronger security requirements for connected applications.
LTI 1.1 relies on an older OAuth 1.0 shared-secret authentication model. LTI 1.3 uses modern security standards including OAuth 2.0, OpenID Connect, signed JSON Web Tokens, and public/private key cryptography.
Major LMS providers are now actively retiring legacy LTI support:
- Blackboard will prevent registration of new LTI 1.0 and LTI 1.1 tools beginning January 1, 2027, and will disable existing LTI 1.0 and LTI 1.1 integrations on September 30, 2027.
- D2L Brightspace will prevent creation of new LTI 1.1 integrations beginning in February 2027, with existing LTI 1.1 launches ending in September 2027.
- Canvas by Instructure has announced a platform-wide initiative to remove support for legacy LTI specifications and move integrations to LTI 1.3, citing the changing security, privacy, and technology environment.
Echo360 is responding proactively to these changes by modernizing our LMS integration architecture across the Echosystem.
We are moving supported LMS integrations for EchoVideo, EchoPoll, EchoExam, PointSolutions, and GoReact toward a shared, native Echosystem LTI 1.3 architecture and retiring the legacy integration paths that are no longer appropriate for the current security environment.
This transition includes:
- Migrating remaining EchoVideo LTI 1.1 integrations to LTI 1.3
- Moving EchoPoll and EchoExam from EdLink-based LMS integrations to Echo360's native LTI 1.3 integration
- Transitioning PointSolutions and GoReact to the shared Echosystem LTI 1.3 architecture
- Standardizing modern authentication, authorization, key management, LMS registration, monitoring, and integration services across Echo360 products
Customers should complete standard migrations by August 31, 2027. Legacy Echo360 LTI 1.1 integrations and affected EdLink integrations will reach end of service on September 30, 2027.
Start Planning
You do not need to wait for a future migration notice to begin planning.
Contact Echo360 Technical Support at support@echo360.com to begin an LMS integration readiness review.
Echo360 will help determine which of your integrations are affected and what action, if any, is appropriate now.
Do not remove, replace, or reconfigure an existing production integration solely because of this announcement. Migration requirements vary by product, LMS, and current configuration.
Why This Is Changing Now
This is not an Echo360-specific technology change. It is part of a broader industry transition toward stronger security requirements for applications connected to institutional systems.
Legacy LTI 1.1 uses shared credentials between an LMS and an external application. LTI 1.3 replaces that approach with modern authentication, authorization, token validation, and asymmetric cryptography.
The major LMS providers are now putting deadlines around that transition, making proactive planning increasingly important for institutions using third-party learning applications.
Canvas has also described its broader LTI migration initiative in the context of rapid advances in AI and an increased focus on data privacy and security.
Echo360 is beginning this program now so institutions have time to:
- Understand their current integrations
- Identify which Echo360 products and LMS connections require change
- Validate critical workflows
- Test migrations outside of production where possible
- Coordinate migration timing with academic calendars
- Complete changes before LMS-provider deadlines create unnecessary risk to teaching and learning
What You Should Do — By Echo360 Product
The required action is not the same for every Echo360 product.
EchoVideo
EchoVideo with LTI 1.1
Your integration will need to migrate to LTI 1.3.
Action: Contact support@echo360.com now to begin identifying your current configuration and migration path.
Echo360 will work with your institution to validate applicable workflows including:
- Course and section links
- Lesson and content links
- Deep Linking
- Course copy
- Cross-listed courses
- Existing supported course links
- User and role provisioning
- Applicable grade workflows
Do not independently replace an existing production LTI 1.1 integration without reviewing the supported migration procedure with Echo360.
EchoVideo with LTI 1.3
No immediate change is required solely because of this announcement.
Echo360 will identify whether any configuration changes are required as part of the broader Echosystem integration modernization.
For new EchoVideo LMS integrations
Use EchoVideo's supported LTI 1.3 integration rather than establishing a new LTI 1.1 connection.
See EchoVideo documentation on Learning Management Systems.
EchoPoll and EchoExam
EchoPoll and EchoExam require a different migration path because many customers currently use EdLink between the LMS and Echo360.
Even where the LMS-facing connection uses LTI 1.3 today, the integration may still depend on EdLink behind the scenes.
Echo360 is replacing this architecture with a direct, native Echo360 LTI 1.3 integration.
EchoPoll or EchoExam with EdLink
Action: Contact support@echo360.com so Echo360 can identify your current configuration and include your institution in migration planning.
Do not disconnect EdLink or attempt to replace the integration independently.
The migration program will validate applicable:
- User authentication
- Course and section identity
- Roster synchronization
- Student and instructor identity matching
- Assessments and sessions
- Historical participant records
- Gradebook workflows
- Existing data associations
For new EchoPoll or EchoExam LMS deployment
Contact Echo360 Support before establishing the integration so we can confirm the supported deployment path for your LMS and implementation timing.
GoReact
GoReact already supports LTI 1.3, but some institutions continue to use LTI 1.1 and migration behavior can vary by LMS and by workflow.
GoReact with LTI 1.1
Action: Contact support@echo360.com now to begin migration planning.
Do not simply remove the LTI 1.1 installation and create a new LTI 1.3 installation without first validating the migration path. Existing course activities, copied assignments, resource links, users, and grade workflows must be considered as part of the transition.
GoReact with LTI 1.3
No immediate reinstall or migration is required solely because of this announcement.
GoReact will ultimately participate in the shared Echosystem LTI 1.3 architecture. Echo360 will provide guidance if an institution-level registration or configuration change is required.
For new GoReact integrations
Use the supported GoReact LTI 1.3 integration where available for your LMS. Echo360 Support can provide the appropriate configuration guidance.
PointSolutions
PointSolutions requires a more configuration-specific review.
Not every PointSolutions LMS integration represents a straightforward LTI 1.1-to-LTI 1.3 migration, and institutions may have different LMS integration and authentication configurations.
PointSolutions will be brought into the shared Echosystem LTI 1.3 architecture as part of this program.
If you currently use PointSolutions with your LMS
Do not change an existing production integration solely because of this announcement.
Echo360 will identify which PointSolutions configurations require customer action as the shared integration service becomes available.
For new PointSolutions integration (or significant changes to an existing one)
Contact support@echo360.com first so we can confirm the supported integration approach for your LMS and avoid introducing a configuration that will require unnecessary rework during the transition.
Customer Transition Timeline
| Date | Milestone | What this Means |
|---|---|---|
| Now | Program announces and Readiness intake opens | Customers may immediately contact support@echo360.com to begin an LMS integration review and migration planning. |
| October - November 2026 | Impact analysis and proactive outreach | Echo360 begins identifying affected institutions and reviewing legacy integration configurations. |
| December 2026 | Detailed migration information continues | More detailed institution-, LMS-, and product-specific migration guidance is distributed as migration paths are validated. |
| January 2027 | Coordinated migration scheduling | Echo360 begins formal scheduling of migration windows based on product readiness, customer configuration, and academic calendars. |
| 01 Jan 2027 | Blackboard restricts new legacy integrations | Blackboard no longer permits registration of new LTI 1.0 or LTI 1.1 tools. |
| February 2027 | Brightspace restricts new legacy integrations | D2L no longer permits configuration of new LTI 1.1 integrations. |
| January - August 2027 | Migration | Echo360 and affected institutions execute migrations in coordinated waves. |
| 31 Aug 2027 | Standard migration deadline | Standard customer migrations should be complete. |
| September 2027 | LMS legacy shutdowns begin | D2L and Blackboard plan to stop existing LTI 1.1 launches during September. |
| 30 Sep 2027 | Legacy integration shutdown and end of service | Legacy Echo360 LTI 1.1 and affected EdLink integrations are disabled. |
Begin Your Readiness Review
- Open a readiness review with Echo360
- Email support@echo360.com and identify the Echo360 products your institution uses.
- You do not need to know your current LTI version or integration architecture before contacting us. Echo360 can help determine that as part of the review.
- Inventory your Echo360 LMS integrations
- Identify where your institution uses:
- EchoVideo
- EchoPoll
- EchoExam
- PointSolutions
- GoReact
- Include production, test, staging, departmental, and sub-account integrations where applicable.
- Identify where your institution uses:
- Do not independently replace production integrations
- LTI 1.1-to-1.3 migration is not simply a credential replacement.
- Depending on the product and LMS, migration can affect resource links, course copies, assignments, identities, rosters, grades, and historical associations.
- Echo360 will provide the appropriate migration procedure for your configuration.
- Identify a test environment
- Where possible, identify an LMS sandbox, test tenant, development environment, or appropriate test course where the migration can be validated before production changes are made.
- Identify your preferred change windows
- Consider academic terms, examinations, registration periods, institutional change freezes, and other periods when LMS changes should be avoided.
- Echo360 will use this information when coordinating migration windows.
Your Customer Success Manager may also assist with planning, but Echo360 Technical Support will coordinate the technical review of your current integration configuration and appropriate migration path.
Frequently Asked Questions
Do we need to contact Echo360 now?
We recommend that institutions with LMS integrations contact support@echo360.com now to begin the readiness process.
You do not need to wait until 2027 or until you receive a detailed impact report.
Starting early allows Echo360 and your institution to identify the current integration architecture, determine whether a migration is required, and select an appropriate migration window.
Does every Echo360 product require the same change?
No.
EchoVideo, EchoPoll, EchoExam, PointSolutions, and GoReact are at different starting points and have different migration requirements.
That is why Echo360 recommends an institution-specific integration review rather than asking customers to make a single blanket LMS configuration change.
Why is Echo360 retiring LTI 1.1?
LTI 1.1 uses an older shared-secret security model that is being retired across the education technology ecosystem.
LTI 1.3 uses modern authentication and cryptographic standards and is the current LTI standard supported by 1EdTech.
Blackboard, D2L, and Instructure have all announced initiatives to move away from legacy LTI implementations.
What happens if our institution already uses LTI 1.3?
You should not assume that you need to reinstall or replace an existing integration.
Depending on the Echo360 product and current configuration, you may already be on an appropriate integration path.
Contact Echo360 if you would like us to confirm your current state.
Why are EchoPoll and EchoExam different?
Many EchoPoll and EchoExam deployments currently use EdLink as part of the LMS integration architecture.
Echo360 is replacing that dependency with its native Echosystem LTI 1.3 service, so those migrations involve more than simply changing an LTI version.
What if we already use GoReact LTI 1.3?
No immediate change should be made solely because of this announcement.
Echo360 will provide guidance if your existing registration needs to change as GoReact is incorporated into the shared Echosystem integration architecture.
What if we use PointSolutions?
PointSolutions configurations vary, so customers should not make a blanket LTI change.
If you are planning a new integration or significant change, contact Echo360 Support first. Echo360 will separately identify existing PointSolutions customers that require action as the shared integration architecture is introduced.
Will historical videos, assessments, activities, grades, or participant records be deleted?
No. This program does not require deletion of historical Echo360 content or records.
Migration paths are being designed and tested to preserve applicable historical content, links, activities, assessments, sessions, identities, participant records, and grade workflows.
The exact behavior differs by product and LMS and will be validated as part of the supported migration process.