Career transition

ERP systems Architect → Data Analyst

Not generic reskilling advice, but an analysis of the distance between two specific occupations: tasks, skills, pace, money and risk.

01 · Starting distance

Transition realism index

Five factors answer a more useful question than “will it work?”: where the route is naturally strong and where proof is needed.

77%realistic route

This is a realistic route. The strongest support is Skill transfer (87%), while the main constraint is Resilience gain (35%). The index estimates the distance between roles, not your ability.

Skill transfer87%

Task similarity87%

Entry accessibility86%

Market opportunity67%

Resilience gain35%

Starting roleERP systems Architect · 28%

→

Learning estimate3–6 months

→

Target roleData Analyst · 51%

02 · What changes in the work

Task comparison

The work shifts from Control and accountability toward Routine operations, a 7-point change. This is the main behavioral adjustment in the move.

ERP systems ArchitectData Analyst87% · profile similarity

Analysis and data

People and communication

Creation and design

Hands-on work

Control and accountability

-13

Routine operations

ERP systems Architect: high-exposure tasks

Data Analyst: high-exposure tasks

03 · Foundation and gaps

Skill-gap map

The map shows the gap between your starting point and a level you can demonstrate to an employer through work evidence—not simply “know / do not know.”

Already transferable

knowledge of the sector, terminology and typical work situations
technical-debt management
systems thinking
software-system understanding
debugging

Needs development

SQL and data preparation
visualization and forecasting
analytical question framing
metric interpretation
requirements work
a practical case for the Data Analyst role

SQL and data preparation

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses sQL and data preparation.

3 wk

start 47%target 92%

visualization and forecasting

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses visualization and forecasting.

3 wk

start 43%target 82%

analytical question framing

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses analytical question framing.

3 wk

start 54%target 92%

metric interpretation

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses metric interpretation.

3 wk

start 53%target 76%

requirements work

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses requirements work.

4 wk

start 42%target 77%

a practical case for the Data Analyst role

Prove it in “Working prototype: ERP systems Architect → Data Analyst transition case”: include a distinct output that uses a practical case for the Data Analyst role.

4 wk

start 36%target 87%

04 · Choose a pace

Three transition scenarios

The same route affects work, money and fatigue differently. A duration without weekly effort says very little.

Keep your current job

8mo.4 h/week
139 hours total

Two short weekday sessions and one hands-on weekend block.

First applications: 6 months
Trade-off: Income is protected, but market feedback arrives later.

First apply SQL and data preparation in the current role, then build the portfolio.

balanced default

Balanced route

5mo.7 h/week
152 hours total

Three weekly sessions: theory, practice and one end-to-end project.

First applications: 4 months
Trade-off: The pace allows market feedback without abruptly ending the current career.

After the foundation in SQL and data preparation, move into the project and first interviews.

Accelerated entry

4mo.12 h/week
208 hours total

Four study blocks weekly, weekly practice and mentor review.

First applications: 3 months
Trade-off: The new qualification develops faster, but fatigue and a shallow portfolio are real risks.

Start applying before training ends and improve evidence every week.

05 · If the direct jump is too large

Bridge occupations

These are not mandatory stops. They matter when they provide paid experience in the new kind of work before the full move.

ERP systems Architect→AI Agent Supervisor→Data Analyst

in 89%out 87%≈ 10 mo.

The AI Agent Supervisor role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

ERP systems Architect→AI Evaluation Engineer→Data Analyst

in 89%out 87%≈ 10 mo.

The AI Evaluation Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

ERP systems Architect→Digital Twin Engineer→Data Analyst

in 70%out 56%≈ 27 mo.

The Digital Twin Engineer role lets you learn part of the new task set in a more familiar context, then approach Data Analyst with stronger evidence.

First leg →Second leg →

06 · Evidence over certificates

Portfolio project

One project cannot replace experience, but it gives an employer something concrete to discuss and shows you can finish real work.

24 hours

Working prototype: ERP systems Architect → Data Analyst transition case

Take a real but anonymized situation from your current field and solve it as a Data Analyst would. The central project task is a role-specific task.

Your advantage is domain context from ERP systems Architect. Make it visible: show which beginner mistakes it helps you avoid.

What the project folder should contain

A repository or interactive prototype with architecture, tests and a demo
A concise decision memo covering inputs, constraints and two rejected alternatives
A result check using measurable criteria plus one failed approach and what changed
A public 5–7-screen case study with all confidential data removed

What makes the project strong

visible use of sQL and data preparation
a real-world problem rather than a tutorial exercise
a measurable outcome and explicit limitations
enough depth to support technical interview questions

07 · Italia · pay before tax

Income trajectory

Within the modeled horizon, income may not return to the current level; plan a financial buffer in advance. This is a scenario model, not a pay promise.

Now€4 370

During study€4 283

First offer€2 757

+1 year€3 147

+2 years€3 450

Model horizon€3 900

Show long-term salary comparison through 2035

ERP systems Architect€4 370 → €5 460

Data Analyst€3 330 → €3 900

Explore current market ↗Search target-role jobs ↗

08 · Technology horizon

How automation risk changes

The target role is not necessarily safer. By 2035, its modeled risk is 31 points higher. Risk reduction should not be the only reason to move.

2026

28%ERP systems Architect51%Data Analyst

2028

34%ERP systems Architect68%Data Analyst

2030

41%ERP systems Architect73%Data Analyst

2035

50%ERP systems Architect81%Data Analyst

09 · An honest check

What you may not like

A good career choice is more than a list of benefits. Before studying, check whether you can live with the target role’s daily reality.

Debugging consumes real time

Much of the output is invisible until late; days include root-cause analysis, documentation and detail work.

The daily rhythm will change

The target role contains substantially more personal accountability and checking others’ work. That can be tiring even when the occupation sounds appealing in theory.

Entry pay may dip

Modeled average pay in the target occupation is lower. A financial buffer or an internal project may help avoid losing seniority.

10 · Where to start

Suggested sequence

01
Review 20–30 Data Analyst vacancies and record actual tasks, mandatory requirements and tools.
02
Define the bridge from ERP systems Architect: knowledge of the sector, terminology and typical work situations. Prepare two examples where this experience produced a measurable result.
03
Learn SQL and data preparation and visualization and forecasting to the level of completing an independent practical task—not merely finishing a course.
04
Build a working prototype, publish the code in a repository, and add tests, documentation and a decision record.
05
Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.
06
Rewrite your résumé for Data Analyst, add the case and begin with test applications, internships, projects or adjacent tasks at your current employer.

All timelines, salaries and percentages are scenario estimates. They depend on starting skills, location, experience, weekly study time and employer requirements. Validate the route through practitioner conversations, a test project and real vacancies.