Four Use Cases.
One Product.
How SLaiCE handles company mandates (data residency), SAP migration (Selective Data Transition), carve-outs and test systems. Each one moves only the data that’s needed, inside your SAP landscape.
Company Mandate (Data Residency)
Keep Required SAP Data in India, Without a Full Copy
Exports and in-house scripts miss later corrections; SLaiCE keeps just the required data in SAP-native system in India, up to date and with audit and trail logs.
Retain required SAP data in India to support statutory requirements, in a live, SAP-native environment, without the cost of copying the whole system.
For These Laws
- Companies Act, 2013 – Section 128(1) read with Rule 3 of the Companies (Accounts) Rules, 2014 (as amended in 2022)
- Income-tax Act, 2025 – Section 62 read with Rule 46(8) of the Income-tax Rules, 2026
Global SAP system
Hosted outside India
IN10 + IN20: 2,316 records
India system
SAP-native, hosted in India
IN10 + IN20: 2,316 records
How It Works
- 1
Identify Required Data
Choose the company codes, books and years the law covers.
- 2
Set Up the India Target
Prepare an SAP-native environment hosted in India.
- 3
Move the Data
SLaiCE moves only the selected data, with masking if required.
- 4
Back Up and Prove It
Daily backups with audit, change and trail logs, and an email confirming each run.
SAP Migration (Selective Data Transition)
Move to SAP S/4HANA Without Moving Everything
Copy-everything conversions drag years of unused data through a long cut-over; SLaiCE moves only the critical subsets and parks the rest in a lean, read-only SAP ECC.
Selective Data Transition takes only the data you still need into SAP S/4HANA, so you start with fresh processes, leave years of data behind and keep downtime short.
Who Does the Functional Work?
SLaiCE is the selective data layer of your SAP S/4HANA migration. The functional, ABAP and SAP BASIS work around it can come from:
- our SAP functional people,
- your consultants, or
- one of our partners.
Migration Time
Conventional approach
With SLaiCE
Actual timeline depends on your scope and number of executions.
How It Works
Choose What Moves
Select objects, years and organisational units for SAP S/4HANA.
Copy to a Shell System
SLaiCE keeps an intermediate system in sync with SAP ECC production.
Convert on Your Date
Stop syncing and upgrade the shell to SAP S/4HANA using SAP’s tools.
Go Live
Dates moved? Re-plan without restarting, then reconcile totals. Legacy years stay in a lean, read-only SAP ECC.
Carve-Out
Separate a Business With Only the Data That Belongs to It
A full copy hands the new owner data that isn’t theirs; SLaiCE selects by company code, unit and date, sorts out the dependencies and leaves the rest in the source.
When a unit is sold, spun off or set up on its own, SLaiCE moves just its company codes, years and objects into the new SAP system, instead of copying the whole system and deleting the rest.
Source SAP system
Everything else stays here
3000: 1,248 records
New SAP system
The separated business
3000: 1,248 records
How It Works
- 1
Define the Scope
Pick the company codes, plants and years that go with the business.
- 2
Prepare the Target
Set up the new SAP system that will run the separated business.
- 3
Move and Mask
Move the selected data and its change history, and mask fields if required.
- 4
Reconcile and Hand Over
Check against the source, then hand the system over.
Test Systems
Test Systems a Fraction of the Size
Full copies take days, eat storage and put personal data in test systems; SLaiCE refreshes in hours with a smaller and scrambled slice.
Refresh QA and development with a purpose-fit, scrambled slice of production, so testers work with realistic data and personal data stays protected.
An example monthEach refresh is ready in hours. No days blocked for a full copy.
Test system refreshedDevelopment refreshedPersonal data scrambled
On a Refresh Day
- 1
Define the Slice
Pick a profile: master data only, the last few years, or one region or country.
- 2
Extract
SLaiCE resolves dependencies between objects for you.
- 3
Scramble
Apply field-level rules to protect personal data.
- 4
Load and Verify
Load the target and reconcile totals automatically.
- less test system data per sprint
- ~80%
- instead of a 5-day full refresh
- On demand
- real personal records exposed
- 0
Top Questions
See all questions and answersNo. SLaiCE runs on SAP tools and is built not to affect the performance of your SAP ECC or SAP S/4HANA systems. Our technical team can walk your SAP BASIS team through the detail.
No. Data moves directly from your source system to your target system inside your own network. Nothing is copied to our systems or stored anywhere else, and data that is encrypted at the source stays encrypted along the way.
SLaiCE runs on SAP tools that come with a free runtime licence from SAP. They can sit on their own server or inside the source or target system, so new hardware is usually not needed. We generally recommend the target system, and set out the options with pros and cons during discovery.
Data can be masked or scrambled as it is extracted, using rules set by business need, data object and field sensitivity. Data already masked or encrypted in the source stays that way. This helps you meet GDPR and other local data-privacy requirements.
No. SLaiCE works at table level, so custom tables, partner add-ons and India-specific add-ons can be sliced, masked and moved with their dependencies, with no extra development. They are configured and signed off during set-up, and modules added later need only small configuration changes.