NexaQora · a separate product from SaviQora
NexaQora: move legacy HR data into SuccessFactors with fewer surprises
SaviQora tests your SuccessFactors implementation. NexaQora helps you migrate the data into it: explainable mapping, record-level validation, a dependency-aware load plan and import files, with a person approving each consequential step.
The demo uses synthetic data only, expires after 24 hours and never connects to a real SAP tenant. NexaQora has its own sign-in and its own data; a SaviQora account is not needed.
How it works
From legacy extract to approved import files
Bring the data
Upload legacy HR extracts (CSV, TSV or JSON) and your target SuccessFactors metadata (OData $metadata or data-model XML). Everything is profiled, hashed and kept in tenant-private storage.
Map with evidence
Each source column gets a suggested target with the evidence behind it: name, datatype, picklist overlap, entity context. Alternatives are shown with the reason each lost. You accept, correct or reject.
Validate every record
Twenty deterministic rules check types, lengths, picklists, references, duplicates, dates and mandatory fields across the whole dataset. Rejected records come with a row number and a reason.
Plan the load order
The sequence is derived from the metadata you supplied, with the evidence for each dependency. Cycles, conflicts and unknowns are flagged rather than hidden.
Approve and generate
An approver signs off the mapping and the plan. NexaQora produces import files, a manifest and a reconciliation that is computed from stored results, and traces every output row to its source row.
Principles
Built to be explainable and controlled
Language-model help that stays in its lane
Language-model help is optional and limited to choosing among candidates the engine already produced. It never approves, never raises a confidence score and never writes to SAP. Pay, national identifiers, employment status and termination dates are never sent to it.
Humans approve
Mappings, plans and exceptions need an authorised reviewer, with separation of duties in the production application: the author cannot approve their own work.
Repeatable and traceable
Every run records the mapping version, metadata snapshot and source-file hashes it used. Rerun it and you get the same result.
Demo and production are separate
The free demo runs on synthetic data and can never reach a real SAP tenant. Production is a separate application with its own database, storage and keys.
Isolated by the database
Tenant isolation is enforced by PostgreSQL row-level security, not only by application code. Stored credentials are encrypted per organization.
Plain about limits
Confidence is a ranking signal, not a probability, and it is labelled that way. Dates and file conventions are settings to verify against your tenant, not assumptions.
What we do not claim
Stated here rather than left for you to discover during procurement.
- Error-free migration
- No tool can promise that. NexaQora reduces manual effort and makes decisions visible and controlled; your team still owns the outcome.
- A verified SAP connection
- File-based import is the primary path. Direct API loading exists but has only been tested against a mock service, is off by default, and must be verified in your own non-production tenant before use.
- An SAP-published load sequence
- The plan is derived from your metadata. You can add sequence rules from SAP documentation; none is presented as official unless you supply it.
- Certification or an SLA
- No SOC 2 or ISO 27001 certification is held and no uptime commitment is offered.
Pricing
NexaQora is priced separately from SaviQora and is not yet on the public price list. Ask us about plans, or see how SaviQora handles security; NexaQora’s controls are documented with the product.
NexaQora is an independent product. It is not an SAP product and is not certified by, endorsed by, or affiliated with SAP SE. SAP and SAP SuccessFactors are trademarks of SAP SE, used here only to describe what the product works with.