Business information systems master alongside your job
You hold a first degree and want to move into architecture, governance or IT leadership. Here is which bachelor counts, how strictly unrelated degrees are checked, and which step up this level realistically carries.
When the master is the right level, and when it is not
A master adds depth. In IT the only question is in which direction.
The master is the right level if you no longer just run systems but own them: application and data architecture, IT governance and compliance, programme steering across projects, security concepts at organisational level. It orders knowledge you bring from projects and supplies the methodology.
It is the wrong level in three cases:
- Without a first degree. Then the route runs through the business information systems bachelor. Routes without a bachelor exist and are narrow, see a master without a bachelor.
- If you want more technical depth. For software architecture in the narrow sense or data analysis at model level, a computer science or data science master is the better fit, see computer science by distance learning.
- If you want to become a generalist. That is what the MBA is built for, the comparison is under MBA or master. What the subject covers is under business information systems by distance learning.
Which bachelor counts, and which only with conditions
This level checks more strictly than most subjects, and for good reason.
The fewest follow-up questions arise, in my experience, with a bachelor in business information systems, computer science, or a commercial degree with documented computer science content. Engineering degrees with a software and data component often get through as well.
Admission with conditions applies as soon as one of the two pillars is missing. Many programmes name concrete minimum volumes of computer science, mathematics or statistics and business administration. The asymmetry is worth noting: a computer science bachelor without commercial modules gets in more easily than a commercial degree without computer science, because business administration is easier to catch up on. Where something is missing, bridging modules are added.
Then the second number: bachelor and master combined are usually expected to add up to 300 ECTS. With 180 a 120 ECTS master fits, with 210 a 90 ECTS one. Submit your module list before applying, it saves a rejection. What work experience is worth at admission is under a master after career experience.
Duration and credit, and why the lever is smaller here
The large time saving from the bachelor does not repeat itself at this level.
A master covers 60, 90 or 120 ECTS. Alongside an IT job, 15 ECTS per semester is dependable, 20 works in phases but rarely in a year with a large rollout. So 120 ECTS at 15 is eight semesters, meaning four years, and three at 20. A 90 ECTS master takes six semesters at 15.
The contrast with the bachelor is stark: there IT training carried whole blocks of modules, here almost nothing. Vendor certificates practically never fit at master level, because they target a product rather than a field, and work experience does not replace methodology modules. Creditable is more likely a relevant university certificate. Whether anything applies is shown by the credit check, the basics are under crediting ECTS.
Work out your own semester load with ECTS per semester. Providers across the German-speaking region are compared with sources on Hochschulnavigator.
The four levels in business information systems side by side
The same question of every row: what does it cost, and what does it deliver.
| Level | Size | Duration part-time | Access | Purpose |
|---|---|---|---|---|
| Certificate | 5 to 30 ECTS, sometimes none | weeks to a year | usually open, often no university access needed | one tool or method, such as project management |
| Bachelor | 180, sometimes 210 ECTS | 4 to 9 years depending on load and credit | university entrance or vocationally qualified | first degree, access to the bridging role |
| Master | 60 to 120 ECTS | 2 to 4 years | a first degree, often with conditions | architecture, governance, IT leadership |
| MBA | 60 to 120 ECTS | 2 to 4 years | first degree plus several years of practice | management across functional boundaries |
Calculated with 10 to 15 ECTS per semester, the band that holds up alongside a full-time job.
Between the third and the fourth row lies the decision that costs the most in IT when it goes wrong. A subject master makes you deployable more deeply inside IT, an MBA connectable outside it. Both take three to four years and are hard to correct. The levels are under part-time master and part-time bachelor.
Which step up the master realistically carries
It shifts the role, and in IT it does so more slowly than many expect.
Realistic are application and data architecture, IT governance, information security at organisational level, programme rather than project steering, consulting with technical responsibility, and in many companies the divisional or IT leadership.
Not realistic is a step up on the certificate alone. Architecture grows out of decisions you have made and owned. Taking the master without relevant project experience leaves you with methodology but no references, and in IT both get asked about. Best is the parallel route: study, and take on responsibility deliberately.
On salary: the degree alone rarely changes it, the changed role does, see salary after your degree. Whether the master carries the step is something I settle with you in the initial consultation.
The business information systems master
The questions that come up on this level in almost every consultation.
Can I enter the master with an unrelated bachelor?
Often yes, but this level checks more strictly than others. Many programmes expect a minimum of computer science, mathematics or statistics and business administration, some with concrete ECTS thresholds. If something is missing, bridging modules are added. Have your module list checked before applying.
Does a pure business bachelor count as access?
Often yes if enough computer science content is documented, otherwise only with conditions. The reverse case, a computer science bachelor without commercial modules, is admitted more easily, because business administration is simpler to catch up on. The threshold is set out in each programme's admission regulations.
Does the master make me an IT architect?
It provides the foundation, not the role. Architecture grows out of decisions you have made and owned, and those are learned in projects. The master orders that knowledge and gives it methodology, and in many companies it is the precondition for being considered at all.
Does work experience get credited in a master?
Far less often than in a bachelor. Master modules aim at depth and methodology, there are few equivalents outside higher education, and vendor certificates almost never fit at this level. What can be credited is more likely a relevant university certificate or modules from an earlier degree.
Master or MBA for IT leadership?
The master stays in the subject and deepens architecture, data and governance. The MBA broadens you across finance, people and sales and requires several years of practice. Want to lead IT on the technical side, take the master. Want to move into overall steering, take the MBA.
Which level holds up in your case
Admission, conditions and the fitting level, settled in one conversation.
The information on this page is general in nature and based on my advisory practice (last updated 31.07.2026). It does not replace an official credit transfer or recognition decision by the respective university and is not legal advice. Specific decisions are made by universities, the ZAB (Germany), the BMBWF (Austria), or the SBFI (Switzerland). I clarify binding next steps with you in the initial consultation.