When
November 2–4, 2026
Three days of hands-on, interactive learning and conversations with SAP practitioners.
Silver Sponsor · Booth 710 · Fort Worth · November 2–4, 2026
Meet ArchiveHub at ASUG Tech Connect 2026.
Bring a real SAP archiving, S/4HANA historical-data or legacy-application retirement question—and explore a practical path from unresolved dependency to governed access.
Where
Fort Worth, Texas
The detailed venue, agenda and attendee information should be confirmed through ASUG when published.
ArchiveHub
Silver Sponsor · Booth 710
Meet the ArchiveHub team at Booth 710 to discuss SAP data archiving, historical reporting, transformation and application retirement.
Event information: Dates and city are based on the official ASUG Tech Connect 2026 sponsor information available when this page was last updated. Agenda, venue, registration and show-floor details may change; confirm current information with ASUG.
Practical conversations
Start with the question your SAP team is already carrying.
ASUG Tech Connect brings together technical practitioners looking for hands-on answers and clarity about what comes next. ArchiveHub conversations will connect that goal to historical-data decisions that can be tested and owned.
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 →Demonstration theme
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.
ArchiveHub will demonstrate 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 →Prepare before the event
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
Planning your ASUG Tech Connect conversation.
When and where is ASUG Tech Connect 2026?
ASUG lists the event for November 2–4, 2026 in Fort Worth, Texas. Confirm the detailed venue, agenda, registration and travel information directly with ASUG when available.
Where can I find ArchiveHub at ASUG Tech Connect 2026?
ArchiveHub is participating as a Silver Sponsor at Booth 710. Meeting-location or demonstration-schedule details will be added if additional information is confirmed.
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.
Meet ArchiveHub in Fort Worth
Bring one SAP or legacy-ERP decision to the conversation.
Tell us which archiving, historical-reporting, transformation or retirement question you want to explore.