01
Landscape inventory
Identify business applications, data stores, integration services, analytics tools, AI environments, external providers, and important infrastructure dependencies.
Enterprise Data Architecture
Understand Your Current Data Architecture Before Making Major Changes
Dataconsultant documents and assesses the data platforms, integrations, flows, controls, ownership, costs, dependencies, and technical debt operating across your organisation today. The result is an evidence-based architecture baseline that helps data, technology, risk, and business leaders make better decisions about modernisation, migration, governance, resilience, and future investment.
- Evidence-led architecture assessment
- Vendor-neutral findings and recommendations
- Security, privacy, and risk considerations
- Decision-ready diagrams and prioritised outputs
Current-state architecture mapIllustrative assessment view
Evidence baselineBusiness sourcesCRM · ERP · ecommerce · files
Operational dataApplications · APIs · partner feeds
External sourcesMarket · regulatory · third party
Integration layerBatch · streaming · ETL/ELT · APIs
Data platformsWarehouse · lakehouse · marts
ConsumptionBI · analytics · AI · operations
LineageCoverage review
ControlsGap analysis
Technical debtPrioritised register
Example structure only. Actual findings are based on supplied evidence, interviews, and agreed validation activities.
Direct answer
What is current-state data architecture?
Current-state data architecture is the documented view of how data is created, moved, stored, transformed, controlled, secured, and consumed across an organisation today. It includes technology, information flows, interfaces, ownership, operational practices, costs, risks, and constraints—not just a diagram of systems.
A structured assessment turns fragmented knowledge into a shared baseline. It helps leaders understand what is working, where risk and duplication exist, which dependencies matter, and what must be addressed before defining a target state or committing to major change.
1
Observe
Collect evidence from systems, documentation, and stakeholders.
Collect evidence from systems, documentation, and stakeholders.
2
Map
Document platforms, flows, controls, dependencies, and ownership.
Document platforms, flows, controls, dependencies, and ownership.
3
Assess
Identify gaps, risks, technical debt, duplication, and constraints.
Identify gaps, risks, technical debt, duplication, and constraints.
4
Prioritise
Create decision-ready findings and practical next actions.
Create decision-ready findings and practical next actions.
Service offering
A complete view of the architecture you operate today
The assessment combines technical review, stakeholder knowledge, operating evidence, and control considerations so that the documented architecture reflects real delivery conditions rather than an idealised diagram.
02
Flow and lineage mapping
Trace how priority data moves between sources, pipelines, platforms, reports, models, operational processes, and downstream consumers.
03
Architecture assessment
Evaluate patterns, coupling, duplication, resilience, scalability, maintainability, interoperability, lifecycle status, and technical debt.
04
Control and risk review
Review ownership, access, classification, retention, observability, change controls, privacy, security, third-party dependencies, and auditability.
Key value propositions
Decisions grounded in how the data estate actually works
Reduce uncertainty before investment
Clarify hidden dependencies, unsupported components, undocumented pipelines, data duplication, and constraints before selecting platforms or approving transformation budgets.
Create a shared architecture baseline
Give business, data, architecture, security, operations, risk, and procurement teams a consistent view of the estate and its priorities.
Sequence change realistically
Use dependency and risk findings to shape target-state design, migration waves, remediation backlogs, governance mobilisation, and implementation planning.
Problems addressed
Common signals that the current architecture is not sufficiently understood
Architecture documentation is incomplete or out of date
Impact: Change programmes rely on assumptions, critical interfaces are discovered late, and teams disagree about how data reaches important reports and processes.
Response: Establish an evidence register, validate priority flows, and create maintainable diagrams with ownership and confidence levels.
Platforms and pipelines have grown without coordinated design
Impact: Duplicate storage, overlapping tools, fragile integrations, inconsistent transformation logic, and rising run costs reduce delivery speed and reliability.
Response: Map patterns, dependencies, lifecycle status, operational effort, and technical debt to identify consolidation and remediation opportunities.
Security, privacy, and control teams lack end-to-end visibility
Impact: Sensitive data movement, third-party transfers, retention, access, and lineage gaps may be difficult to evidence or manage consistently.
Response: Connect architecture flows to classifications, owners, control points, obligations, and specialist review requirements.
Modernisation plans start with a preferred product rather than evidence
Impact: New technology may recreate old problems, overlook operational dependencies, or produce a transition plan that the organisation cannot execute safely.
Response: Define current constraints and decision criteria before target-state design, procurement, migration, or implementation.
Need a defensible baseline before a data-platform decision?
Share the business trigger, priority domains, major platforms, and known constraints. Dataconsultant can recommend an appropriate assessment scope.
Who the service is for
Suitable for organisations preparing to change, govern, or stabilise their data estate
Good fit
- You are planning cloud migration, lakehouse adoption, platform consolidation, or major modernisation
- You need a reliable baseline before designing target-state architecture
- You have recurring data incidents, conflicting reports, fragile pipelines, or unclear lineage
- You are integrating organisations, business units, platforms, or data following a merger
- You need to connect architecture decisions with security, privacy, resilience, and compliance
- You need independent evidence for investment, procurement, audit, or remediation decisions
May not be the right fit
- You only require a narrow product configuration or single-pipeline code fix
- A current and validated architecture baseline already exists for the required scope
- You require a statutory audit, legal opinion, formal certification, or penetration test only
- Required stakeholders, evidence, and environment access cannot be made available
- You need immediate implementation without time to understand critical dependencies
- The primary requirement is outside enterprise data architecture
Common use cases
Where a current-state architecture assessment creates practical value
Cloud and platform migration
Identify source dependencies, integration patterns, data volumes, latency requirements, controls, and transition constraints before defining migration waves.
AI and advanced analytics readiness
Assess whether priority data is discoverable, governed, traceable, accessible, timely, and technically suitable for analytics and AI use cases.
Merger and acquisition integration
Compare overlapping platforms, data domains, interfaces, ownership, regulatory constraints, and consolidation choices across combined organisations.
Regulatory or audit remediation
Document relevant flows, control points, data stores, third parties, evidence gaps, and accountable owners for targeted remediation planning.
Cost and technical-debt reduction
Locate redundant platforms, duplicate pipelines, unsupported components, manual workarounds, expensive movement patterns, and operational hotspots.
Target-state architecture preparation
Establish facts, constraints, reusable capabilities, transition risks, and decision criteria before designing the future architecture.
Capabilities
Assessment coverage tailored to business priorities and architecture risk
Business and stakeholder context
Clarify the decisions the assessment must support, priority processes, critical data products, pain points, regulatory drivers, transformation initiatives, ownership, and success criteria.
Systems, data, and integration
Inventory material sources, stores, pipelines, APIs, files, queues, event streams, transformation layers, models, reports, AI environments, and external exchanges.
Platform and engineering patterns
Review storage, compute, orchestration, processing, deployment, observability, environment separation, recovery, scalability, lifecycle, and operational support patterns.
Governance, security, and assurance
Connect architecture components to ownership, classification, access, retention, residency, privacy, security, quality, metadata, change control, auditability, and third-party risk.
Deliverables
Outputs designed for architecture decisions, remediation, and planning
The final deliverable set is agreed during scoping and reflects the required depth, available evidence, and intended decisions.
| Deliverable | Purpose | Typical contents | Primary users |
|---|---|---|---|
| Executive assessment summary | Support decisions and sponsorship | Key findings, implications, priorities, dependencies, and recommended next actions | Board, executives, sponsors, procurement |
| Architecture landscape pack | Create a shared baseline | System context, platform, integration, data-flow, deployment, and consumption views | Architecture, engineering, operations, security |
| Inventory and evidence register | Document scope and confidence | Systems, interfaces, data stores, owners, evidence sources, assumptions, and validation status | Data office, architecture, audit, programme teams |
| Risk and technical-debt register | Prioritise remediation | Finding, impact, likelihood, affected assets, dependency, owner, urgency, and proposed response | Technology, risk, security, finance |
| Control observations | Connect architecture to assurance | Access, classification, retention, lineage, resilience, privacy, third-party, and auditability observations | Security, privacy, compliance, internal audit |
| Prioritised recommendation backlog | Guide next-stage action | Quick wins, foundational work, sequencing, dependencies, decision points, and follow-on scope | Sponsors, programme leads, delivery teams |
Require a specific diagram set or evidence standard?
Dataconsultant can align deliverables to your architecture governance, assurance process, procurement stage, programme methodology, or regulatory context.
Service process
How Dataconsultant delivers the assessment
The sequence is adapted to scope and evidence availability. Each stage has a clear objective and primary output.
Align scope and decisions
Confirm business triggers, priority domains, stakeholders, constraints, required assurance, and decisions the assessment must support.
Primary outputAssessment charter and evidence requestCollect and validate evidence
Review inventories, diagrams, specifications, policies, logs, contracts, costs, incidents, and representative environments.
Primary outputEvidence register with confidence levelsMap the landscape
Document sources, integrations, platforms, flows, transformations, consumption, ownership, and external dependencies.
Primary outputCurrent-state architecture viewsAssess architecture and controls
Evaluate patterns, resilience, lifecycle, scalability, maintainability, quality dependencies, privacy, security, and operational practices.
Primary outputFindings and architecture observationsPrioritise risks and technical debt
Rank issues using impact, urgency, exposure, dependency, cost, effort, and alignment with planned change.
Primary outputPrioritised risk and remediation registerValidate and transfer knowledge
Review findings with accountable teams, resolve material discrepancies, document limitations, and agree practical next actions.
Primary outputDecision pack and transition recommendationsTechnology, platforms, and frameworks
Vendor-neutral assessment across mixed data estates
Technology environments
The service can review relevant combinations of:
Reference frameworks and standards
Depending on scope and jurisdiction, the assessment may draw on recognised data-management, enterprise-architecture, security, privacy, resilience, risk, and service-management practices.
Framework applicability and legal interpretation should be validated by authorised internal or external specialists.
Working across legacy, cloud, and vendor-managed platforms?
The assessment can focus on the interfaces and dependencies that matter most rather than requiring every component to be reviewed at the same depth.
Engagement models
Choose the depth and delivery model appropriate to the decision
Focused architecture review
For a defined domain, platform, transformation decision, control concern, or priority data flow. Suitable when scope and evidence boundaries are clear.
Enterprise current-state assessment
For cross-domain architecture baselining, major modernisation, merger integration, target-state preparation, or strategic investment planning.
Assessment plus remediation roadmap
Adds prioritised work packages, sequencing, ownership, dependencies, decision gates, and mobilisation guidance to the baseline assessment.
Embedded architecture assurance
Provides ongoing review and decision support while internal teams or implementation partners refine documentation and deliver change.
Illustrative examples
How assessment findings may support different decisions
Migration preparation
A manufacturer planning cloud migration discovers that finance reporting depends on undocumented file transfers and manually maintained reference data. The assessment records dependencies and control gaps before migration sequencing.
AI readiness
A services company identifies multiple versions of customer data, limited lineage, and inconsistent access controls. Findings help separate data-foundation work from AI-model experimentation.
Cost rationalisation
A multi-business organisation maps overlapping warehouses, duplicate ingestion, low-use data marts, and unsupported tools. The resulting backlog informs consolidation analysis and ownership decisions.
These examples describe plausible situations and do not represent verified client results.
Expected outcomes and KPIs
Measure whether the baseline improves decisions and delivery
Measures should be agreed against a documented baseline. Architecture assessment does not itself guarantee business benefits; value depends on sponsorship, implementation, adoption, and operational follow-through.
Architecture coveragePriority systems, interfaces, flows, and owners documented
Evidence confidenceFindings supported by validated sources and accountable reviewers
Risk visibilityMaterial architecture and control risks assigned and prioritised
Dependency clarityCritical upstream, downstream, and third-party links identified
Technical-debt actionHigh-priority remediation items accepted into planning
Decision cycle timeReduced time spent resolving basic architecture uncertainty
Documentation ownershipNamed owners and update process established
Programme readinessTarget-state, migration, or procurement work starts with an agreed baseline
Pricing and cost factors
Assessment cost depends on scope, complexity, and evidence depth
Architecture scope
Number of domains, business units, systems, platforms, interfaces, data flows, and jurisdictions included.
Assessment depth
Document review only, stakeholder validation, environment inspection, control mapping, lineage tracing, or detailed technical analysis.
Delivery conditions
Stakeholder access, evidence quality, security restrictions, onsite needs, vendor coordination, and review cycles.
Required outputs
Diagram count, inventory detail, risk scoring, executive materials, roadmap development, assurance support, and follow-on design.
Request a scope-based estimate
Provide the main business trigger, approximate number of domains and platforms, required deliverables, and desired decision date. A written estimate can then be prepared after initial scoping.
Why consider Dataconsultant
A practical, transparent approach to architecture evidence
Business-linked scope
The assessment is shaped around the decisions, risks, and transformation outcomes the organisation needs to address.
Evidence-conscious findings
Sources, assumptions, confidence levels, limitations, and unresolved questions are documented rather than hidden.
Cross-functional perspective
Architecture is considered alongside governance, engineering, operations, security, privacy, cost, and organisational ownership.
Usable outputs
Deliverables are structured for executive decisions, architecture review, remediation planning, procurement, and knowledge transfer.
Discuss the architecture decision you need to make
Dataconsultant can help determine whether you need a focused review, enterprise baseline, target-state design, or a combined assessment and roadmap.
Security, quality, privacy, and compliance
Architecture findings should account for control obligations and delivery risk
✓
Security
Review identity and access patterns, encryption, network boundaries, secrets, environment separation, logging, monitoring, recovery, and privileged operations where relevant.
✓
Privacy
Identify sensitive-data movement, purpose and ownership questions, retention, residency, third-party transfers, minimisation considerations, and specialist legal-review points.
✓
Data quality
Assess where validation, reconciliation, observability, reference data, metadata, and issue-management dependencies affect trusted use of data.
✓
Compliance and assurance
Map architecture evidence to internal policies, contractual duties, audit findings, sector requirements, and applicable frameworks without presenting consulting observations as legal certification.
The service does not replace legal advice, formal compliance certification, statutory audit, specialist cybersecurity testing, or regulator-approved assurance unless separately scoped with authorised professionals.
Delivery environment
Designed for complex, mixed, and evolving technology ecosystems
Internal teams
Work with enterprise architects, data architects, engineers, platform teams, security, privacy, risk, operations, finance, and business-domain owners.
External providers
Coordinate evidence and dependencies with cloud vendors, SaaS providers, systems integrators, consultants, outsourcers, and managed-service partners.
Operating constraints
Adapt review methods for restricted environments, regulated data, global jurisdictions, legacy systems, limited documentation, and active transformation programmes.
Representative customer perspectives
What buyers value in current-state architecture work
The following are realistic representative testimonials written for this service. They are not presented as verified client statements.
“The team helped us turn scattered diagrams and individual knowledge into one understandable view of our data landscape. Communication was structured, review comments were handled carefully, and the final risk register gave our migration programme a much stronger starting point.”
“We needed more than a technology inventory. The assessment connected integrations, ownership, resilience, privacy, and operational support in a way that both architecture and business leaders could use. Delivery was professional and revisions were incorporated without losing clarity.”
“The current-state maps exposed dependencies that had not appeared in our earlier platform planning. The consultants were transparent about evidence gaps, validated assumptions with our teams, and produced practical recommendations rather than pushing a preferred vendor.”
“Our reporting estate had grown over many years and no single team understood the whole flow. The engagement was well managed, workshops stayed focused, and the final outputs helped us prioritise technical debt and ownership issues with confidence.”
“The strongest part of the work was the connection between architecture and control requirements. Security, retention, third-party movement, and auditability were discussed in practical terms. The quality of documentation and revision handling met our procurement expectations.”
“We used the assessment before defining our target state. It gave senior stakeholders a common baseline, highlighted where evidence was weak, and prevented several premature design decisions. Communication, delivery quality, and knowledge transfer were consistently professional.”
Frequently asked questions
Current-state data architecture questions
What is a current-state data architecture assessment?
It is a structured review of the data systems, platforms, integrations, flows, controls, ownership, quality dependencies, costs, risks, and technical debt that exist today. It creates a documented baseline for target-state design, migration, modernisation, governance, and investment decisions.
What is included in the service?
Scope can include stakeholder discovery, system and platform inventory, data-flow mapping, integration review, architecture principles, storage and processing patterns, metadata and lineage, security and privacy controls, resilience, cost drivers, technical debt, risks, dependencies, and prioritised findings.
When should an organisation commission this assessment?
Common triggers include cloud migration, platform replacement, AI adoption, merger integration, regulatory remediation, inconsistent reporting, recurring data incidents, high operating cost, unclear lineage, duplicated pipelines, or a planned target-state architecture programme.
How long does the assessment take?
Duration depends on scope, organisation size, platform diversity, number of domains, stakeholder availability, documentation quality, jurisdictions, security constraints, and the required depth of validation. A reliable timeline is agreed after initial scoping.
What deliverables are typically provided?
Typical deliverables include an architecture inventory, current-state diagrams, data-flow maps, integration catalogue, platform and capability assessment, risk and technical-debt register, control observations, dependency map, findings report, prioritised recommendations, and decision-ready executive summary.
Does the service include target-state architecture?
The current-state assessment can identify implications and design constraints for a future state. Detailed target-state architecture, transition architecture, migration planning, or implementation design can be commissioned as a separate or follow-on scope.
Which technologies can be assessed?
The review can cover on-premises and cloud databases, warehouses, lakehouses, integration tools, streaming platforms, data-quality tools, catalogues, BI platforms, AI and machine-learning environments, master-data systems, enterprise applications, APIs, file transfers, and custom pipelines.
How are security, privacy, and compliance handled?
The assessment identifies relevant data classifications, access patterns, encryption controls, retention, residency, logging, third-party transfers, segregation, and auditability. It does not replace legal advice, formal certification, penetration testing, or statutory audit unless separately commissioned.
What client information is required?
Useful inputs include system inventories, diagrams, data models, integration specifications, lineage records, policies, incident logs, cost reports, contracts, audit findings, access to representative environments, and interviews with business, data, architecture, security, operations, and risk stakeholders.
How is pricing calculated?
Pricing is influenced by the number of domains, systems, platforms, integrations, jurisdictions, workshops, evidence sources, review depth, onsite requirements, security restrictions, required diagrams, validation activities, and whether remediation or target-state work is included.
Can Dataconsultant work with our internal architects and vendors?
Yes. The engagement can be delivered alongside internal architects, data teams, security teams, platform vendors, systems integrators, and managed-service providers, with agreed responsibilities, evidence requirements, review points, and escalation paths.
How are findings prioritised?
Findings can be ranked using business impact, regulatory exposure, security significance, operational risk, cost, architectural dependency, implementation effort, urgency, and alignment with planned transformation. The prioritisation method is agreed with accountable stakeholders.
Still deciding what level of assessment you need?
Describe the change programme, known architecture concerns, required decisions, and available evidence. Dataconsultant can help define a proportionate scope.