Not transferring directories, but maintaining controllability
The transition from SAP to 1C:ERP and 1C:UH is not a technical data import. In SAP, over the years of operation, a corporate management model is usually formed: processes, documents, roles, analysts, contractual models, cost distribution rules, reporting, integrations and control procedures.
With a straight-line migration, a business risks losing the transparency of management accounting, the coherence of contracts, assets, costs and obligations, the correctness of historical data, familiar reports, control procedures and user trust in the new system. Therefore, migration should begin with architectural and methodological diagnostics.
Why RESTART
Experience in large-scale SAP projects
The RESTART team participated in projects based on SAP ERP, SAP RE-FX, SAP ECC/BI, SAP BW, SAP BusinessObjects, SAP DMS, SAP FI, SAP FI-AA and SAP integration components.
Understanding business logic
We have worked with budgeting, management accounting, contracts, assets, leases, IFRS/IFRS 16, repairs, operations, reporting and integrations.
1C / Bitrix affiliate environment Invent
Invent strengthens the group in the projects 1C:ERP, 1C:UH, 1C:ZUP, 1C:Document Flow, integrations, portals, personal accounts and the development of Russian ERP environments.
Methodological depth
We describe the target model of processes, data, reporting, roles and control procedures, and are not limited to setting up the system.
Business consulting
The team is adept at speaking to CFOs, CIOs, Chief Accounting Officers, Treasury, Procurement, Asset Management and Operations.
Integration experience
We design the interaction of 1C with DWH/BI, EDI, CRM, personnel systems, industrial systems, data buses and legacy environment.
What we help to transfer from SAP to 1C
We analyze the current SAP architecture and design a target environment based on 1C solutions and related systems. It is important not to copy the old system one to one, but to maintain manageability, data and control where the business really needs it.
| SAP environment | What it usually contains | Target environment 1C / related solutions |
|---|---|---|
| SAP FI | Accounting, postings, period closing, financial reporting. | 1C:ERP, 1C:Accounting, 1C:UH. |
| SAP CO | Controlling, central financial district, cost items, distribution, management accounting. | 1C:ERP, 1C:UH, BI/DWH. |
| SAP MM / SD | Purchases, sales, contracts, warehouses, nomenclature, mutual settlements. | 1C:ERP, CRM environment, integration layer. |
| SAP FI-AA | Fixed assets, depreciation, asset classification, analytics. | 1C:ERP, 1C:UH, 1C:Accounting. |
| SAP RE-FX | Real estate, property objects, rent, contracts, areas, operation, costs. | 1C:ERP, 1C:UH, industry and 1C project solutions. |
| SAP PM / MRO | Equipment, repairs, operation, applications, materials, maintenance. | 1C:ERP, 1C:TOIR, industry solutions. |
| SAP BW / BO | Reporting, KPI, data marts, management analytics. | BI/DWH, 1C analytics, corporate reporting. |
| SAP DMS | Documents, archives, scans, connections between documents and accounting objects. | 1C: Document flow, corporate archive, Document AI. |
| SAP Workflow | Approvals, statuses, deadline control, roles and rights. | 1C: Document flow, BPM environment, corporate portal. |
| SAP XI / PI | Integrations, exchanges, routing, exchange control. | API, ESB, ETL/ELT, modern integration layer. |
How we conduct a migration project
SAP landscape diagnostics
We analyze the SAP modules used, modifications and Z-objects, reference books, documents, integrations, reports, roles, authorities and operational problem areas.
Target architecture 1C
We determine what is covered by standard 1C functionality, where adaptations are needed, what data is migrated, what remains in the archive, and what reports go to 1C, BI or DWH.
Functional mapping
We build the SAP → 1C matrix: objects, directories, documents, postings, registers, analytics, reports, control procedures and process owners.
Data preparation
We identify duplicates and contradictions, normalize reference books, define transformation rules, prepare control samples and reconciliations before and after loading.
Implementation and testing
We configure and finalize 1C, develop downloads, integrations, conduct functional, integration and user acceptance testing.
OPE and launch
We support parallel accounting, closing the first period, correcting discrepancies, training, supporting key users and stabilizing processes.
SAP experience that enhances the transition to 1C
Enterprise property and asset management
Experience from SAP RE-FX, SAP DMS, SAP BW, SAP BO, SAP FI and FI-AA helps to transfer complex models of objects, contracts, areas, repairs, operations, costs and reporting.
Budgeting and cost distribution
We understand budget planning, distribution of planned and actual costs, management accounting, controlling and reporting in large organizations.
Lease agreements and IFRS 16
Experience in leases, obligations, discount rates, modifications, currency agreements, rights to use assets and IFRS 16 reporting helps to correctly design a 1C environment.
Integrations and enterprise data
We worked with SAP integrations with banking, budget, accounting, documentary, GIS/CAD, BI and external government systems.
Methodology and regulations
When migrating from SAP, methods, classifiers, regulations, instructions and second-level documents are critical, because many rules have lived within the system for years.
Control procedures
For large businesses, reconciliations, approval routes, access rights, control of period closure and transparent acceptance of the result are important.
Project experience relevant to SAP → 1C migration
On a public site, we do not disclose confidential details and do not use logos without verified rights. But in the RESTART portfolio there are projects that show the depth of SAP, ERP, rental accounting, property, budgeting, reporting, methodology and integrations.
| Capability of experience | What does it show for migration? |
|---|---|
| Sber Bank: IFRS 16 and financial services | Reporting, real estate, financial planning, forecasting, SAP consultants, ABAP, Java and testing in the banking environment. |
| MegaFon: SAP S/4HANA and IFRS 16 | Lease agreements, object-by-object cost accounting, contract controls, accruals, integration and acceleration of reporting. |
| VTB: property management on SAP S/4HANA | Single source of data, real estate register, contracts, 659-P, IFRS 16, budget and management analytics. |
| Lukoil: corporate template S/4HANA | Real estate, land resources, income and expense leases, risk matrix and control procedures. |
| Alrosa and AgroInvest: lease accounting | FAS 25, IFRS 16, tax accounting, PBU 18, calculations of the right to use an asset and lease obligations. |
| Russian Post: methodological documents | Regulations for the management of real estate, accommodation, rent, risks, capital construction, operating and maintenance costs. |
Who is the service suitable for?
SAP → 1C migration is especially relevant for companies where SAP is used not as a simple accounting system, but as a management platform for finance, procurement, sales, assets, contracts, reporting and integrations.
Holdings and groups of companies
Complex structure of legal entities, branches, central federal districts, management reporting and consolidation.
Industry, oil and gas, energy and mining and metals industry
Assets, MRO, purchasing, production data, cost accounting, CII and industry requirements.
Banks and financial sector
Financial services, reporting, integration, access control, regulation and the high cost of error.
Retail, telecom and companies with facilities
Many contracts, areas, objects, rentals, repairs, costs, integrations and users.
What does the customer get?
As a result of the project, the customer receives not only a customized 1C system, but also a controlled transition path: from the current SAP landscape to the target architecture, data, integrations, testing and support of the first period.
| Artifact | Why is it needed? |
|---|---|
| Map of the current SAP landscape | Understanding of modules, extensions, data, integrations, reports, roles and critical dependencies. |
| Target architecture 1C | A clear model of 1C:ERP, 1C:UH, document flow, BI/DWH, integrations and archival environments. |
| Functional matrix SAP → 1C | Comparison of objects, documents, transactions, analytics, reports and control procedures. |
| Data migration strategy | Transformation rules, control samples, reconciliations, historical and archival data. |
| Integration plan | Which exchanges are saved, which are rebuilt, which go to API/ESB/ETL. |
| Project documentation and training | Technical specifications, regulations, instructions, training of key users and acceptance scenarios. |
| Launch and support of the first period | Support for parallel accounting, period closing, discrepancies and work stabilization. |
Migration risks and how we control them
| Risk | What could happen | How RESTART reduces the risk |
|---|---|---|
| Loss of SAP business logic | Data is transferred to 1C, but the rules for accounting, control and distribution are lost. | We carry out a functional comparison of SAP → 1C and fix the transformation rules. |
| Errors in master data | Duplicates, incorrect reference books, discrepancies in analysts. | We do cleaning, normalization, control samples and reconciliations. |
| Loss of management reporting | Management does not receive the usual reports after launch. | We design reporting in advance: 1C, BI or DWH. |
| Integration gap | Exchanges with external and internal systems stop. | We build an integration map and test exchanges before launch. |
| User resistance | Business does not accept the new system. | We involve process owners, train key users and conduct trial operation. |
| Errors when closing a period | The financial block cannot close the first month. | We support parallel accounting and first closure. |
| Underestimation of SAP improvements | Critical Z-objects and custom processes are not taken into account. | We analyze the improvements and choose: standard 1C, adaptation or process change. |
Work formats
Express migration audit
Quick assessment of SAP outlines, preliminary risks, hypothesis of the target 1C architecture, top-level roadmap and next steps.
Pre-project survey
Detailed basis for technical specifications, budget and plan: processes, SAP landscape, SAP → 1C matrix, requirements, data, integrations, deadlines and resources.
Complete Migration Project
Design, configuration and development of 1C, data migration, integration, testing, training, launch and maintenance of operation.
Strengthening the customer team
Analysts, architects, 1C/SAP consultants, developers, testers, DevOps, information security and data specialists under a managed project framework.
How can the project be strengthened?
The transition from SAP to 1C often affects not only the ERP team. RESTART can connect related practices so that migration does not create new chaos around data, security, reporting and operations.
Frequently asked questions
Is it possible to completely replace SAP with 1C?
Yes, but the correct answer depends on the current SAP landscape, the number of improvements, integrations, reporting and business requirements. Sometimes standard 1C functionality is enough, sometimes you need an architecture with 1C:ERP, 1C:UH, 1C:Document Management, BI/DWH and an integration layer.
How long does migration from SAP to 1C take?
The period depends on the scale of the system, the number of legal entities, the volume of data, the number of integrations and the depth of SAP improvements. We recommend starting with an express audit or pre-project survey.
Do I need to migrate all historical data from SAP?
Not always. Typically, data is divided into migrated to 1C, archived, reporting and data for reconciliations. This approach reduces risks and speeds up launch.
Is it possible to save SAP BW/BO reporting?
Yes. We analyze reports, indicators, data sources and offer a target solution: reports in 1C, a separate BI/DWH environment or a combined model.
How does RESTART differ from a typical 1C contractor?
RESTART combines the 1C / Bitrix partner practice of Invent with the historical experience of enterprise-level SAP projects. We understand SAP processes, data, integrations and reporting, so we design the migration deeper than a simple transfer to 1C.
Is it possible to start with a short diagnosis?
Yes. An express audit helps to understand the scale, risks, target architecture and a realistic transition scenario to a large project.
Discuss the transition from SAP to 1C
If you are planning to replace SAP, switch to 1C:ERP or 1C:UH, preserve management reporting and reduce migration risks, start by diagnosing the current landscape. We will help you assess the scope of the project, identify risks, prepare a roadmap and choose a realistic transition scenario.
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.
