Short answer
Map is the first step. NexDiscovery connects read-only to the systems you choose, within the fields agreed for the engagement, and learns what your approved data means and how your systems relate.
Key takeaways
- Access is read-only and limited to the fields agreed for the engagement.
- You choose the systems. The client controls the scope.
- Data gaps are noted and carried forward.
On this page ▾
What happens
- You choose which systems and data sources are connected, such as CRM, ERP, billing, finance, support, or warehouse platforms.
- Connectors authenticate with read-only credentials, scoped to the fields agreed during sprint design.
- The business question is confirmed, so the work stays within scope.
- Where data is incomplete or inconsistent, the gap is noted.
What it needs
- Read-only access to the systems in scope.
- Agreement on field scope with your security and data teams.
- Confirmation of the primary business question.
What you get
A clear, agreed scope and a connected, read-only view of the approved data that the next steps work within.
Why it comes first
The most valuable signals can live between the systems you choose to connect. Scope and access come first so that everything after it stays within what you authorized. Autonomous discovery does not mean autonomous access.
Frequently asked questions
What is the Map step?
What access does NexDiscovery have?
Does Map require us to document our data first?
What comes after Map?
Related guides
What is Data Intelligence?
Data Intelligence is how NexDiscovery learns what your approved data means and how your systems relate to each other.
Read guideCorrelate: how NexDiscovery finds patterns across systems
Correlate is the second step.
Read guideData readiness checklist for a Discovery Sprint
You do not need clean data or a finished data catalog to start.
Read guide