ERP Migration & SelectionFree assessmentPDF, Excel, Word exportabas ERPDiscrete ManufacturingGermany, Austria, Switzerland

abas ERP Migration Assessment: How Hard Will Your Move Be?

abas ERP is a widely used mid-market ERP in German-speaking manufacturing. Many shops are now deciding whether to upgrade, re-platform or leave. This assessment rates the effort and risk of that move in ten questions.

0 of 10 answered0%

1. How heavily is your abas system customized with its own scripting and screen changes?

Think of custom FOP programs, changed screens, custom Infosystems and your own database fields.

2. How well documented are your custom programs and business rules?

3. How many external systems exchange data with abas (shop floor, CAD/PLM, web shop, EDI, banking, DATEV)?

4. How clean is your master data (articles, customers, suppliers, bills of material)?

5. How much transaction history must be available in the new system?

6. How current is your abas version and maintenance contract?

7. How complex are your manufacturing processes (variants, multi level BOMs, subcontracting, serial and batch tracking)?

8. Do you have a named business owner and key users with time freed for the project?

9. How many legal entities, countries and languages does the system cover?

10. Have you defined why you are moving and what must be better afterwards?

How to use this assessment

Answer each question for your productive system, not the system you wish you had. Involve the IT lead and at least one key user from production or purchasing, because their answers will differ on documentation and data quality. Your score is a percentage of the maximum, and the band tells you how much preparation to plan before talking to vendors. Print the PDF and share it with your steering group so everyone starts from the same picture.

What drives migration effort in abas environments

In practice three things dominate: custom code written over the years, the number and quality of interfaces, and master data quality. abas allows deep adaptation through its own scripting language and Infosystems, which is a strength during operation but means a replacement must reproduce or retire those behaviours. Interfaces to CAD, shop floor systems, banking and accounting such as DATEV often hide undocumented assumptions.

Custom programs and screens that carry real business rules
Point to point interfaces without documentation
Duplicate or inconsistent article and partner records
Open ended history requirements
Missing business ownership

Reading the result

The bands are not a verdict on whether to leave abas. A low score means preparation is the cheapest risk reduction, and sometimes staying on abas for another cycle while you clean up is the right call. A high score means you can negotiate from strength and run a shorter selection. Retake the assessment after your discovery phase to see how the picture changes.

Common mistakes

Teams often treat migration as a data copy exercise and discover late that process differences are the real cost. Another frequent error is scoping every historic report for rebuild instead of checking which ones were used in the last year. Finally, do not let a vendor deadline set your scope. Ask your abas partner for a usage report of custom programs before you decide what to carry over.

Frequently Asked Questions

Is this assessment official from abas Software?

No. It is an independent self check built from common migration risk factors in mid-market ERP projects. It is not affiliated with or endorsed by abas Software, and it does not replace a formal assessment by your implementation partner.

Should I move to a different ERP or upgrade abas?

The score only measures effort and risk, not the right target. Upgrading within abas is often cheaper if customization is light and your needs have not changed. Move when processes, support or strategy no longer fit.

How long does an abas migration usually take?

It depends heavily on scope. A single entity near standard may take under a year, while multi country, heavily customized estates can run well beyond that. Data cleansing and interface testing usually decide the timeline more than software configuration does.

Can AI help with the migration work?

It can help inventory custom code, document business rules and draft test cases, with a human reviewing the output. It does not remove the need for data cleansing decisions or business sign off.

If you want a second opinion on your abas estate, Netray can review your custom code and interfaces and give you a written effort range. This is optional and the assessment above works without it.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Operations

More ERP Migration & Selection tools

See all

Back to All Tools