SAP→1C express assessment
The assessment provides the basis to decide how to carry out the migration and launch the transition program from SAP to 1C. Two fixed-term editions: a shortened one lasting 10 business days and a standard one lasting 20.
Login Format
The express assessment answers the question facing management before budget allocation: exactly what in your SAP landscape needs to be migrated, what it turns into on the 1C side, and which risks determine the timeline. Two to four weeks instead of a six-month pre-project phase.
The outcome is a high-level scope of work and roadmap, not a detailed technical specification: the latter is prepared at the next stage, once the decision to proceed has already been made.
Methodology, risks, and full route — on the page Migration from SAP to 1C and SAP import substitution; implementation of a target system — 1C:ERP implementation.
What's included
SAP landscape
Which modules are actually used, how many customizations have been accumulated, how roles, reporting, integrations, and historical data are structured.
Target environment in 1C
What each block transitions into: 1C:ERP, 1C:UA, document management, portals, BI and DWH, where an archive of the old system is needed.
Transition risks
Data quality and volume, discrepancies in accounting methodology, integration with external systems, information security requirements, user readiness, and impact on timelines.
Road map
Sequence of stages, pilot area for the first wave, team composition, and criteria by which a stage is considered accepted.
Editions and volume limits
The main edition is preferred for the enterprise perimeter; the reduced edition is intended for a significantly smaller perimeter.
| Parameter | Shortened — 10 working days | Main — 20 working days |
|---|---|---|
| Perimeter | one legal entity | One productive SAP ERP client or tenant, up to two legal entities with comparable accounting methodology |
| Functional blocks and processes | two blocks, four end-to-end processes | up to four blocks, up to eight end-to-end processes |
| Interview | up to six | until twelve |
| Integrations, reports, Z-objects | up to ten integrations, eight reports, ten Z-objects | up to 20 integrations, 15 critical reports, 30 priority Z-objects from the provided register |
| Documents | up to 15 documents, up to 300 pages | up to 25 documents, up to 600 pages |
In the main edition, we consider up to three target 1C configurations; BI, archive, and related solutions—at a conceptual level.
What is needed from the client
- List of used modules, business processes, customizations, reports, and integrations;
- aggregated statistics on the data;
- involvement of the SAP team, process owners, the finance department, and IT;
- identifying priority items from the general registry — which enhancements and reports to address first;
- Information on critical accounting periods and transition restrictions.
What is not included
- Full automated SAP inventory, reading and evaluation of all Z-code;
- detailed fit-gap analysis for each operation and detailed technical specification;
- design of all exchanges;
- data extraction and cleanup, migration runs, balance reconciliation;
- 1C setup and licenses;
- Fixed budget for the entire transition program.
The survey provides a basis for deciding how to launch the program, but does not replace a detailed pre-project.
When the work is completed
- High-level alignment with target solutions has been completed for the agreed blocks and processes;
- Priority enhancements, integrations, and reports are classified as: standard coverage, likely enhancement, adjacent system or archive, detailed assessment required;
- transition waves, dependencies, risks, and a high-level budget range with justifications have been prepared.
The migration program budget is provided as a scenario range: accuracy promises of the type "plus or minus ten percent" do not hold up under scrutiny at this data volume. A conclusion such as "migration should not proceed now" or "we will start with a different environment" constitutes a fully valid outcome of the assessment.
Output documents
| Artifact | Why is it needed? |
|---|---|
| SAP Landscape Map | What is used today: modules, customizations, integrations, reporting, and data volumes—the basis for assessing effort complexity |
| Target architecture outline in 1C | Which configurations deactivate SAP functions, what is migrated, what is rethought, and what is archived |
| Risk and Dependencies Register | Risks related to data, methodology, integrations, and people — indicating what blocks the start and what is resolved along the way |
| Migration Roadmap | Phases, pilot area, estimated timelines, and budget range for solution protection |
Added to the above are a map of survey coverage boundaries (indicating what remained outside the perimeter), a register of methodological gaps, and the composition of the next pre-project phase.
Package budget
| Editorial office | Package budget |
|---|---|
| Shortened, 10 working days | 900,000 – 1.5 million ₽ excluding VAT |
| Main, 20 working days | 0K – 3.5M RUB excluding VAT |
The exact fixed price is determined after the initial meeting and scope verification; included work, deliverables, and exclusions are confirmed prior to commencement; any scope expansion is possible only upon agreement.
Distributed holding, multiple SAP landscapes, and non-matching accounting models are assessed individually.
Team composition
- ERP/SAP Architect — analysis of the current landscape, enhancements, and integrations.
- 1C Architect — target configuration, function coverage, scope of modifications.
- Data Analyst and BI — volumes, quality, reference books, reporting, and what to archive.
- Project Manager and Business Analyst — interviews with process owners, risks, timelines, result protection.
Who is it suitable for?
To the IT Director
You need to understand the scope of the SAP replacement, the architectural risks, and a realistic transition plan.
To the Chief Financial Officer
It is important to maintain accounting, reporting, control procedures, archives, and data integrity.
ERP Department Manager
Need to map SAP modules, customizations, and Z-objects to the target 1C environment.
To Procurement and the Project Office
Project scope, milestones, acceptance criteria, team composition, and procurement strategy are required.
Standard work plan
Interview and inventory
Systems, processes, owners, reporting, integrations, accumulated constraints, and pain points.
Functional mapping
SAP modules and customizations are mapped to 1C configurations and related solutions.
Data and Integrations
Critical reference books, documents, history, exchange interfaces, storage, and reporting.
Road map
Stages, team composition, risks, quick improvements, pilot area, and acceptance criteria.
Relevant experience
Public cases do not reveal confidential details of customers, but show RESTART’s experience in related enterprise landscapes.
Frequently asked questions
Need access to SAP?
Desirable. At a minimum, interviews, uploads and a description of the landscape are required.
Will there be a full technical specification?
The output is a top-level scope and roadmap; Detailed technical specifications can be prepared in the next step.
Is it possible to estimate the budget?
Yes, at the level of ranges and cost factors after understanding the scale.
How we fix the volume and deadline
The terms below are identical for all packages and are incorporated into the contract without changes.
- Perimeter — prior to the agreement. We hold an initial meeting of up to 60 minutes and agree on the perimeter passport: systems, processes, sources, participants, and outcomes.
- Countdown of the term. The timeline starts after the handover of the approved set of source materials, provision of access credentials, and confirmation of the interview schedule. Delays on the client's side will postpone the timeline by a corresponding amount of time.
- Data. We operate within a coordinated secure channel. Production data is not transmitted to external AI services without the customer's written permission.
- Result transmission. We provide materials in PDF and editable formats (DOCX, XLSX, PPTX, or agreed equivalents) and conduct one results defense session of up to 90 minutes.
- Acceptance. Five business days are allocated for reviewing the results. One consolidated round of clarifications within the agreed scope is included; however, correction of errors and non-compliances with the contract is not limited to this round.
- Volume change. New systems, sources, and tasks are included only upon agreed changes to scope and cost.
- Work format. The default format is remote, unless an in-person component is explicitly planned for the package.
The statuses and licenses on the basis of which the works are performed are collected on the page "Licenses and statuses".
Email us
Write to us at info@restart.re or click the button below. For the first letter, it is sufficient to briefly describe the outline, the role of the organization, current systems, limitations and the desired outcome.
Email usRequest format
We agree on the volume, timing and output artifact - and launch it in a short time.
