When
November 2–4, 2026
Three days of hands-on, interactive learning and conversations with SAP practitioners.
Past event · Silver Sponsor · Booth 710 · November 2–4, 2026
ArchiveHub at ASUG Tech Connect 2026.
ASUG Tech Connect brought SAP practitioners together for technical sessions, hands-on learning and community conversations. ArchiveHub was a Silver Sponsor at Booth 710 in Fort Worth, Texas.
Thank you to everyone who joined us. Explore BorgWarner’s customer presentation and photos from the conference, then continue the conversation about SAP archiving, historical data and application retirement.
Customer perspective · ASUG Tech Connect 2026
BorgWarner’s approach to legacy transformation.
How BorgWarner Transformed 10+ Legacy Systems Across SAP, NetSuite, M&A and More
ASUG’s published session describes BorgWarner’s use of ArchiveHub across more than 10 SAP and non-SAP transformation initiatives, including SAP ECC, GTS, PLM, PPM and NetSuite. The session focuses on continued access to historical records, reports and documents after application retirement, and a repeatable approach across a changing enterprise landscape.
Session summary based on ASUG’s public agenda.
Conference moments
From the stage to Booth 710.
A look back at ArchiveHub at ASUG Tech Connect 2026. Select a photo to view it at full size.
Where
Fort Worth Convention Center
1201 Throckmorton St, Fort Worth, TX 76102, United States.
ArchiveHub
Silver Sponsor · Booth 710
ArchiveHub participated as a Silver Sponsor at Booth 710. Request a follow-up about SAP data archiving, historical reporting, transformation and application retirement.
Past event: ASUG Tech Connect 2026 took place November 2–4 at Fort Worth Convention Center. The organizer was Americas' SAP Users' Group (ASUG). This page preserves the event dates and venue for reference; see ASUG's event information or explore ArchiveHub events.
Continue the conversation
Start with the question your SAP team is already carrying.
Explore practical resources for the historical-data decisions facing SAP teams after transformation.
Which SAP data should remain online?
Separate business-complete history from current operational data, identify confirmed archiving candidates and connect residence assumptions to process ownership.
Explore SAP data archiving →What history belongs in S/4HANA?
Classify information into migrate, archive, preserve independently or defensibly destroy using future use, governance and validation requirements.
Use the decision matrix →Why is the legacy application still running?
Expose the reports, documents, interfaces, custom data and historical user journeys that continue to depend on the source before planning shutdown.
Use the readiness checklist →How will people use history after retirement?
Define authorized searches, reports, relationships, documents, exports and service expectations—then validate them with the people who perform the work.
Use the acceptance template →Explore a follow-up demonstration
From legacy lookup to governed historical access.
Organizations often retain an aging SAP or non-SAP system because a small group still needs old transactions, reports, attachments or business context. That dependency can persist long after operational migration is complete.
Request a demonstration of how a historical-data environment may support appropriately authorized business inquiry, reporting, document retrieval and evidence export independently of the retired application. Demonstration scope depends on the source, selected content, architecture and configuration; it should not be interpreted as universal object or integration coverage.
Bring one candidate application
- What business process did it support?
- Who still requests its historical information?
- Which reports, documents and relationships matter?
- Which archives, repositories or custom objects exist?
- What prevents shutdown approval today?
Six implementation patterns
Use generalized experience without exposing customer confidentiality.
ArchiveHub’s implementation-pattern library turns recurring enterprise requirements into practical guidance without presenting unapproved customer work as named case studies.
SAP ECC retirement during S/4HANA transformation
Preserve required ECC history, validate independent access and make shutdown an evidence-based decision.
Explore the pattern →Historical finance and audit reporting
Maintain governed inquiry, reconciliation and supporting evidence without keeping the obsolete ERP online.
Explore the pattern →Preserving SAP documents and relationships
Keep transactions, attachments, links and business context connected through application retirement.
Explore the pattern →Plan your follow-up
Make a short meeting produce a useful next step.
Name the decision
Archiving backlog, S/4HANA scope, historical reporting, application retirement or another defined outcome.
Identify the users
Finance, audit, tax, customer service, operations, legal or another appropriately authorized group.
List the dependencies
Required reports, transactions, documents, custom data, interfaces, retention concerns and unresolved ownership.
Request a focused meeting
Share the scenario in advance so the conversation can begin with relevant questions and a practical decision framework.
Frequently asked questions
Following up after ASUG Tech Connect.
When and where did ASUG Tech Connect 2026 take place?
The event took place November 2–4, 2026 at Fort Worth Convention Center, 1201 Throckmorton St, Fort Worth, TX 76102, United States. It has concluded.
Where was ArchiveHub at ASUG Tech Connect 2026?
ArchiveHub participated as a Silver Sponsor at Booth 710. You can view conference photos on this page and request a follow-up conversation with the team.
Who should meet with ArchiveHub?
SAP application owners, enterprise architects, data-archiving and lifecycle teams, S/4HANA transformation leaders, records and compliance stakeholders, reporting owners and teams planning legacy-application retirement may find the conversation useful.
Can we discuss a non-SAP legacy application?
Yes. ArchiveHub implementation patterns also cover Oracle ERP, IBM i and multi-ERP estates. The discussion should begin with required historical information, user access and shutdown dependencies rather than only the source technology.
Do we need to share confidential customer data?
No. Begin with a generalized landscape description, the candidate application and the unresolved decision. Detailed customer information should be shared only through an appropriate controlled process.
Continue after ASUG Tech Connect
Bring one SAP or legacy-ERP decision to the conversation.
Tell us which archiving, historical-reporting, transformation or retirement question you want to explore.