When a SAS Migration Becomes Relevant
A SAS migration rarely begins with a purely technological decision. Often, costs, operational requirements, cloud strategy, or the availability of suitable development environments change. At the same time, existing business logic and production processes must be preserved.
That is why HMS looks beyond just the code. We analyze applications, data flows, interfaces, operational processes, and regulatory requirements. This provides a basis for decision-making regarding the target state, scope, and approach.
Typical scenarios include:
- An established SAS 9.4 environment needs to be modernized or replaced
- Applications and data processes are to be migrated to a cloud architecture
- SAS code needs to be migrated to Python, R, or other target technologies
- Licensing and operating models need to be reevaluated
- Existing processes must continue to run smoothly during the migration
Python is a potential path forward for companies looking to transition existing analytics and data processes into an open development and operations environment. However, a SAS-to-Python migration involves more than just translating individual commands.
Dependencies, macros, data access, and business calculation logic must be mapped in a traceable manner within the target architecture. HMS combines code transformation with architectural work, technical validation, and integration into the intended platform.
Python is just one option among many. The appropriate target language and platform depend on the use case, operating model, existing expertise, and regulatory requirements.
1. Analyze the SAS Environment
We map applications, codebases, data flows, interfaces, and operational dependencies. The analysis reveals which components are business-critical and where modernization is needed.
2. Define the Target Architecture and Migration Strategy
Together, we define the target platform, architecture, scope of migration, and priorities. We determine which applications should be migrated, transformed, redeveloped, or decommissioned.
3. Prepare the Infrastructure and Integrations
HMS sets up the required target environment and plans interfaces, data access, permissions, and operational processes. Existing systems and security and compliance requirements are taken into account in this process.
4. Migrate Code and Data
We migrate defined applications, code modules, and data sets to the target architecture. Recurring steps can be supported and automated using Code2X.
5. Review the Results and Support the Implementation
HMS reviews migrated components and provides support for integration, validation, enablement, and rollout. The scope depends on criticality, the regulatory environment, and the operating model.
6. Support Operations and Continuous Development
After the migration, we provide support for hypercare, technical operations, and further development. Responsibilities and handoffs are defined early in the project.
The SAS Migration Tool
Code2X supports defined transformation steps
For large codebases, Code2X can assist with the analysis and transformation of recurring code structures. The tool takes project-specific architectural requirements into account and ensures the results are traceable.
HMS integrates Code2X into migration planning, technical review, and implementation. Which components are suitable for automated processing is evaluated based on the specific SAS codebase.
Why HMS
SAS Expertise Combined With Architecture and Software Engineering Capabilities
HMS combines SAS expertise with software engineering, cloud architecture, data engineering, and experience in regulated environments. As a result, we view SAS migrations not as an isolated code conversion task, but as a transformation of a production system landscape.
What you can expect from us:
- Interdisciplinary Migration Teams
SAS experts, cloud architects, migration engineers, data engineers, project leads, and business analysts - Automated Code Transformation with Code2X
Agentic workflows can support recurring analysis and transformation steps - Project-Specific Migration Strategies
Migration paths are aligned with the existing environment, target architecture, and operational requirements
Anwendungsmodernisierung mit GenAI: von SAS zu Python auf AWS
Ein führender Versicherungskonzern modernisierte eine zentrale SAS-Anwendung auf AWS. HMS entwickelte Architektur und Migrationsvorgehen, setzte die Modernisierung um und prüfte GenAI für die SAS-zu-Python-Migration.
SAS Viya auf Azure: Migration und langfristiger Plattformbetrieb
HMS migrierte die SAS-9.4-Umgebung eines großen europäischen Energie- und Versorgungsunternehmens auf SAS Viya in Microsoft Azure. Seit der Migration übernimmt HMS Betrieb, Wartung und Weiterentwicklung der Plattform.
SAS-Landschaft im regulatorischen Meldewesen betreuen und modernisieren
HMS unterstützt einen führenden IT-Dienstleister der Finanzbranche bei der Modernisierung und Optimierung seiner SAS-Landschaft für das regulatorische Meldewesen.
No. A SAS migration can involve modernization within the SAS ecosystem, a hybrid architecture, or the phased replacement of individual applications. Which approach makes the most sense depends on the target state, the codebase, and operational requirements.
Python is often a relevant target platform, but it is not automatically the best choice for every application. R, SAS Viya, or hybrid architectures may also be suitable. HMS evaluates target technologies based on business logic, integration, operations, and existing expertise. Learn more about migrating from SAS to R
The process typically begins with an analysis of the existing SAS environment and a clarification of the target state. This allows for an assessment of the effort involved, risks, migration paths, and an appropriate project scope.
