Understanding the SAP landscape
Modules, improvements, integrations, data, roles, reports, documents, dependent processes.
Result: current state map.Who is it suitable for?
CIO
You need to understand the scope of the SAP replacement, the architectural risks, and a realistic transition plan.
CFO
It is important to maintain records, reporting, control procedures, archives and trust in the data.
ERP Director
It is necessary to compare SAP modules, modifications, Z-objects, integrations and the target 1C environment.
Purchasing and Project Office
We need scope, stages, acceptance criteria, team and procurement logic of the project.
Pain and management risk
The main risk of migrating SAP → 1C is to perceive it as a transfer of directories, although in reality the manageability of the business is transferred.
| Pain | What happens without preparation |
|---|---|
| SAP business logic is not described | Accounting rules, roles, reports, control procedures and exceptions are lost in the target system. |
| Integrations are underrated | Banks, EDI, DWH, CRM, portals and external systems break project deadlines. |
| Data migrates without quality | History, reference books, documents and analysts do not undergo reconciliation and reconciliation. |
| No step-by-step roadmap | The company chooses a transition scenario that is too large or too risky. |
What does RESTART do?
Designing the target 1C environment
1C:ERP, 1C:UH, 1C:Document Management, portals, integrations, BI/DWH and archives.
Result: a variant of the target architecture.We assess the risks of transition
Data, integrations, methodology, users, information security, deadlines, resources and critical dependencies.
Result: risk register.Preparing a roadmap
Stages, team, artifacts, quick wins, pilot area and migration plan.
Result: roadmap 3-12 months.Artifacts at the output
SAP landscape map
Modules, improvements, integrations, data, reports, roles and problem areas.
Target 1C architecture
Target scheme of 1C and related systems: accounting, documents, integrations, BI, archive.
Migration risk register
Risks of data, methodology, integrations, information security, users and timing.
Migration roadmap
Stages, team, pilot area, artifacts and acceptance criteria.
First stage deadline
For most companies, 2-4 weeks are enough to get an objective picture of the migration and make a decision: start a pilot, prepare technical specifications, break up the program or clarify the target architecture.
Team composition
| Role | Area of responsibility |
|---|---|
| ERP/SAP architect | Current SAP landscape, improvements, processes, integrations and risks. |
| 1C architect | Target architecture 1C:ERP, 1C:UH, documents, roles, reports. |
| Data/BI analyst | Data migration, reconciliations, archives, DWH/BI and reporting. |
| PM / business analyst | Interviews, plan, backlog, artifacts, communications and acceptance. |
Standard plan
1
Interview and inventory
Systems, processes, owners, reports, integrations, pain points and limitations.
2
Functional mapping
SAP modules and improvements are compared with 1C and related solutions.
3
Data and Integrations
Critical reference books, documents, history, interfaces, DWH and reports.
4
Migration Roadmap
Stages, team, risks, quick wins, pilot and acceptance criteria.
Relevant cases and experience
Public cases do not reveal confidential details of customers, but show RESTART’s experience in related enterprise landscapes.
Frequently asked questions
Is it possible to replace SAP with 1C completely?
Yes, but the answer depends on the current SAP landscape, improvements, integrations, reporting and business requirements.
What is the most important thing to check before migrating?
Business logic, data, integrations, reporting, access roles, archive loop and user readiness.
Do you only work with 1C?
No. RESTART combines SAP experience, 1C practice Invent, BI/DWH, information security, development and project management.
Application form
Fill out a short application or send an email to info@restart.re. For the first conversation, it is enough to describe the outline, the role of the organization, current systems, limitations and the desired outcome.
Let's discuss your environment
Describe the task, current systems, constraints, and expected results. We will offer a practical first step: diagnostics, pilot, audit, roadmap or project team.
