Eursap's Ask-the-SAP-Expert – Chris Skelton

Eursap's Ask-the-SAP-Expert – Chris Skelton.

This month, we feature Chris Skelton. Chris is based out of the UK and is a seasoned expert in the thorny topic of data migration. He has a long background with SAP but also has branched out into Microsoft as well. His cross-ERP experience is a vital skill in the world of data migration, and he has some lessons for us all!

Thank you, Chris, for taking the time to talk to us. Could you introduce yourself with a bit of background for our readers?

I began my career in software development using Microsoft technologies, and I continue to work on software projects today, though now with a specialised focus on data migration tools and processes. Over the past 20 years, I have dedicated myself to mastering the complexities of data migration, and together with Matt Hodnett, co-founded Konexxia - a specialist data migration consultancy. We established Konexxia to bring genuine expertise to this critical yet often overlooked aspect of ERP transformations.

Chris, with over two decades of experience, what inspired your early focus on SAP and data migration in particular?

In the early days, SAP programmes were the natural fit for enterprises - there simply were not viable alternatives at that scale. What struck me most was watching company after company reinventing the wheel with every implementation. Each project would start from scratch, developing the same labour-intensive, error-prone processes with no knowledge transfer between programmes. Teams would spend months writing bespoke extraction scripts, manually mapping fields in spreadsheets, and discovering the same pitfalls their predecessors had encountered.

Data migration was then, as it remains today, frequently an afterthought in programme budgets and is not considered exciting enough by many consultants. There were no standard methodologies - each systems integrator had their own approach, if they had one at all. Most relied on armies of analysts with spreadsheets, hoping that sheer effort would overcome the lack of proper tools and processes.

Coming from a software engineering background, I saw an incredible opportunity to bring technology and automation into this space. Where others saw tedious manual work, I saw patterns that could be automated, processes that could be standardised, and quality controls that could be systematised. Together with Matt, we recognised that our process-driven software development experience could transform how data migration was delivered.

At Konexxia, we set out to create and continuously refine a set of standard processes that would make data migration predictable, repeatable, and reliable. We saw the chance to deliver genuine excellence in a niche but absolutely critical component of ERP programmes - turning what many considered a necessary evil into a competitive advantage for our clients.

Looking back, which migration project taught you the most—either for its complexity or the creative solution you found?

One SAP programme from 2011-2012 stands out particularly. We faced multiple disparate source systems all converging into a new ECC 6 implementation. The sheer scale was daunting - literally thousands of separate data extracts from numerous legacy systems, including older SAP systems. Traditional approaches would have required months just to develop and test the extraction processes. We realised early that we needed to innovate, so we developed a bespoke data import framework that allowed imports into our staging area to be rapidly specified without writing custom code for each one. That project really shaped our thinking about automation and tooling.

Data migration methods have evolved. How have ETL frameworks and automation tools changed your approach over the years?

From our very first projects, Matt and I identified repetitive, error-prone elements in the data migration process. We began developing standardised procedures for the team to follow, which eventually evolved into the Konexxia migration methodology we use today. Leveraging our software development backgrounds, we have continuously developed tools to automate critical tasks. What is exciting is that each project brings unique challenges, driving constant evolution of both our methodology and our Generix data migration platform. It is this continuous refinement that keeps us at the forefront of the field.

You have experience across the ERP space with many of the major players. How does migration of data to an SAP system differ from other ERP vendors? Is there much of a crossover in terms of methodology?

The fundamental methodology remains consistent regardless of source or target system. The cornerstone of any successful migration is comprehensive understanding of the data landscape - both origin and destination. While understanding source data is vital, equally important is grasping the target system's blueprint to understand how the data will actually be utilised. The principles of discovery, mapping, transformation, and validation apply universally, though each ERP platform has its unique characteristics and requirements.

How do you see SAP’s Intelligent Enterprise (BTP, AI, eventing) changing the future of data migration?

The Intelligent Enterprise opens fascinating possibilities for data migration. BTP now enables us to pull data from both cloud and on-premises sources through a unified platform, eliminating the need for individual custom connectors. AI is poised to revolutionise pattern recognition and data mapping. Envisioning systems automatically detect quality issues, suggesting transformation rules based on historical patterns, or predicting which anomalies will cause load failures. However, the fundamentals remain unchanged - thorough source data understanding, rigorous validation, and business continuity assurance are non-negotiable. Technology enhances our capabilities but cannot replace methodical planning and business engagement.

In a world moving toward API-first and streaming architectures, will traditional batch migration ever become obsolete?

I do not foresee batch migration disappearing. While APIs and streaming are great for ongoing integrations, ERP transformations typically require a definitive break from legacy systems. Migration is not merely data movement - it is restructuring, harmonising across multiple sources, and often fundamentally reimagining business processes. The batch approach provides the control and validation points necessary for these complex transformations.

For enterprise-scale migrations, what are your top three risk areas—and how do you mitigate them?

First, validation is paramount. You can successfully migrate 100% of in-scope data, but without proper validation and testing, the project will fail. We build validation into every stage of our process.

Second, data landscaping is critical. Understanding the legacy source system reveals how the business currently operates and what data exists. Equally important is understanding target system requirements. Effective data mapping requires close collaboration between legacy system owners and functional consultants configuring the new system. This partnership identifies both what is available to migrate and crucial gaps requiring attention.

Third, cutover timing and coordination can derail even perfectly planned migrations. Unrealistic cutover windows or unmapped dependencies cause failures. We mitigate this through rigorous dress rehearsals - executing the complete cutover process multiple times to understand precise timings, identify bottlenecks, and ensure every team member knows their role. While our Generix platform automates and parallelises loads, you still need that detailed cutover plan with clear checkpoints and rollback procedures.

Data quality is often the unsung challenge. How do you enforce robust cleansing and validation before migration?

Data quality begins with visibility. Our automated profiling tools expose issues early - showing stakeholders precisely what percentage of customer records lack email addresses or how many vendors have invalid tax numbers. This transparency creates urgency. We implement a three-pronged approach: automated cleansing for systematic issues, business-led cleanup sprints for high-value data (our "golden data set"), and clear ownership assignments. The crucial factor is early engagement - data quality cannot be remedied in the final sprint before go-live.

We all know, Chris, that data migration is often overlooked as an important piece of the ERP transformation puzzle. How do you communicate migration complexity to non-technical stakeholders to build confidence and maintain transparency?

I have learned that executives need business impact, not technical details. We translate complexity into business language: "Your customer master data is your company's address book - we are merging five different versions, removing duplicates, and ensuring everyone has current information." Visual dashboards displaying migration readiness as simple traffic lights prove highly effective. We conduct regular show-and-tell sessions where users see their actual data in the new system, building tremendous confidence. Most importantly, we consistently relate progress to business outcomes and value delivery.

When unexpected issues arise mid-migration, how do you balance keeping the project on track with delivering a robust solution—without causing panic?

Our first principle: no surprises. We maintain transparent risk registers and communicate potential issues before they escalate to crises. When unexpected challenges arise, we rapidly assess impact through a simple framework: Is this a showstopper? Can we work around it? What is the business impact? We present options, not problems - for instance, "We have discovered 1,000 orphaned transactions. We can exclude them with business sign-off, create placeholder records, or invest two days to investigate." Pre-agreed escalation paths and decision authorities prevent paralysis and maintain momentum.

As someone aspiring to become a migration expert, what skills or experiences would you recommend they focus on first?

Data analysis is fundamental. Successful migration experts excel at identifying patterns and anomalies in information. While query writing is important, it is insufficient alone. Equally critical is the ability to communicate effectively with business users - translating between technical and business domains. Pure technical skills will only take you so far; the ability to understand business context and build stakeholder relationships is what distinguishes truly excellent migration specialists.

Which tools or technologies do you predict will become essential for data migration in the next 3–5 years?

AI is impossible to ignore and will undoubtedly transform data migration. I anticipate AI analysing source data and generating initial mapping specifications, dramatically accelerating the discovery phase. However, there is a critical caveat - the danger lies in practitioners without proper expertise accepting AI-generated outputs uncritically. This could lead to serious consequences for clients. AI will be a powerful tool, but it requires experienced professionals to validate and refine its outputs.

Now a little bit of fun: What is the most unusual or quirky thing you have discovered hiding in leftover legacy data during a migration?

Legacy systems reveal fascinating organisational archaeology. Beyond technical anomalies like orphaned sales orders, we have uncovered remarkable workarounds. One manufacturing system contained products named "Dave's special widget - DO NOT DELETE" - which turned out to be critical custom items for major clients. We have found customer records from the 1970s still marked "active" because someone feared archiving them might break something. My favourite discovery was an entire shadow reporting system built within item description fields - users had creatively worked around IT restrictions to meet their needs. These discoveries offer valuable insights into how businesses really operate versus how systems assume they operate.

Data migration experts are often the guys sitting up late into the night loading data. Do you get any downtime to enjoy hobbies and if so, what are they?

It is essential to maintain balance, even in this demanding field. I am passionate about snowboarding - there is something extraordinary about carving down a mountain surrounded by stunning alpine scenery. The clear mountain nights are equally captivating, offering incredible stargazing opportunities away from light pollution. Both pursuits provide the perfect antidote to the intensive detail work of data migration - they are a brilliant reminder that there is a magnificent world beyond databases and transformation rules!