A Alumio vivid purple arrow pointing to the right, a visual representation of how to access more page material when clicking on it.
Go back

Lost in translation: A story about data transformation

By
Carla Hetherington
Published on
November 16, 2023
Updated on
June 24, 2026
IN CONVERSATION WITH
Email icon
Email icon

You have undoubtedly heard about the hugely popular “Transformers” movie franchise, but have you ever heard about the Transformers of the Alumio integration platform? Spoiler alert: it has nothing to do with cool cars. Instead, transformers have everything to do with data mapping and transformation, which are both crucial processes in data integration. Ready to deep-dive into what data transformation is and how it works? Keep on reading!

What is data transformation?

Data transformation refers to the process of taking existing data in a particular format or state and converting it into a different format or state to facilitate the seamless integration between a source system and a destination system.

Data transformation can take on many shapes and be constructive (adding and replicating data), negative (deleting irrelevant data), aesthetic (standardizing incoming data and fine-tuning it to suit destination requirements), or structural (renaming or integrating columns in a database). Essentially, it is the cornerstone of data integration across organizations, and Alumio makes it easy to achieve.

How does data transformation work?

Picture the following: there are two systems: System A and System B. Certain data is retrieved from System A (source system), but System B (target system) requires it in another format to be able to interpret it. For example, perhaps the data from System A is in XML format, but System B only understands data if it is in JSON format.

In this scenario, you have to convert and map the data to the format required by System B, and you may also have to filter the source data since there might be irrelevant information within it that System B doesn’t require.

What is data mapping?

Data mapping refers to the process of connecting a data field from one source to a data field in another source. As such, it is a visual representation of data movement and transformation and is also known as the first step in the process of data integration.

Why is data mapping important?

Due to the complexity and high volume of data today, data mapping has become more crucial than ever. With data mapping, the potential for errors is reduced, and data is standardized, thus making it easier to understand and interpret. Not unlike a map, data mapping helps visualize the best way to get data from point A to point B, and just like missing an exit can thwart your travels, data mapping errors can jeopardize your data’s movement from point A to point B.

Is this all starting to sound a bit too complicated? Let’s approach data transformation from the standpoint of an analogy. In this case, we will use language translation as an analogy to better understand what data transformation is and how it works.

So, how does data transformation relate to language translation?

Data transformation is like translating a book from one language to another. Imagine you have a book written in Dutch and want to make it accessible to English readers.

In this case, the Dutch book would be the source system, also known as System A, containing the source data (Dutch language). This source data is structured and formatted in a way that the source system understands (just as a Dutch reader would), but lacks the structure and format for System B, also known as the target system, to understand it (just as an English reader wouldn’t understand the Dutch book). Thus, the answer is simple: translate the book from Dutch to English, i.e., translate the source data from System A so System B can understand.

This translation will be carried out by a translator, the entity transformer. The entity transformer defines how the data should be converted while preserving the meaning, just as a translator would.

However, to carry out any translation, translators must follow translation rules based on grammar, context, etc. that specify how to convert specific terms, phrases, or structures from one language to another. These rules would be the data mapping features, which define how data fields, attributes, and structures are converted from the source to the target format.

Just as a translator might need to add context or footnotes to clarify certain passages in the book to readers, sometimes, during data transformation, you might need to enrich the data with additional information relevant to system B, which Alumio’s tools facilitate.

Just as a translated book may need proofreading to catch errors and ensure accuracy, data transformation processes include checks to verify that the transformed data is correct and handle any errors that may arise. In this case, the proofreader would be Alumio, as the platform provides users with the necessary tools to verify and check the resulting data.

Lastly, once the book is successfully translated and validated, it can be published or made available to readers who speak the target language. In the context of data integration, the transformed data is synchronized with the target system, making it accessible and usable for its intended purpose.

How does Alumio transform data?

The Alumio integration platform as-a-service (iPaaS) transforms data by using entity transformers. Entity transformers are used to execute data actions within the integration, such as mapping, enriching, and transforming data into desired formats and filtering out unnecessary data. Entity transformers can also be used to develop caching layers that optimize integrations.

In the Alumio dashboard, entity transformers can be created and altered by going to Connections -> Entity transformers. With these transformers, data can be modified since they allow data selection/reduction, translation/mapping, encoding, calculation, sorting/ordering, and merging/joining/lookup from other sources, which allows for aggregations, the generation of surrogate keys, transposing/pivoting of array/object keys and values, as well as validation.

Interestingly, transformers also have the ability to filter out entire data points that are produced by incoming configurations, often preventing unnecessary queued items.

Learn how to map and filter data using Alumio’s Entity Transformers →

Additionally, transformers enable the combination of data flows that offer business logic that decides whether the transformer will be applied to a certain data set. The convergence of transformers and Alumio’s features allow for the storage of data and the combination of data sets, which can be compared to create, update, and delete data feeds, as well as many more functions.

Overall, transformers are magical tools that enable you to create your own custom code with endless possibilities.

Deep-dive into how to make use of all the functionalities of Alumio’s entity transformers →  

What are the benefits of data transformation with Alumio?

Improved data quality: Transformation processes can help standardize and clean data, ensuring system consistency and accuracy while reducing manual efforts and the likelihood of errors.

Efficient data mapping: Alumio offers tools for easy data mapping between different formats and structures, facilitating seamless communication between disparate systems and promoting interoperability at a rapid pace.

Agility and scalability: Alumio's data transformation capabilities can contribute to increased agility in adapting to changing business requirements and emerging data formats. When adapting to new information and data formats, Alumio promotes scalability to handle growing data volumes and increase integration complexities as businesses expand.

Compliance and security: Ensuring data is transformed securely and in compliance with relevant regulations is crucial, and Alumio provides the necessary features to support these requirements.

Turn AI ambition into action

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

Get a free assessment of your integration needs and next steps

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

No items found.
Topics in this blog:

FAQ

Integration Platform-ipaas-slider-right
What is data transformation in the context of system integration?

Data transformation in system integration is the process of converting data from the format, structure, or values used by the source system into the format, structure, or values expected by the destination system. It is necessary because different systems represent the same real-world entities differently: an order in Shopify and an order in SAP share conceptual meaning but differ in field names, data types, structure, and business rules. Without transformation, data passed between systems causes errors, rejected records, and process failures that require manual correction. Transformation is the logic that bridges these differences automatically.

Integration Platform-ipaas-slider-right
What does Alumio's Transformer do and how is it different from custom code transformation?

Alumio's Transformer is a library of precreated, reusable data manipulation components (field mapping, value conversion, filtering, enrichment, aggregation, conditional routing) that are assembled and configured rather than custom-coded. Rather than writing PHP or Python to convert a Shopify order payload into SAP's IDOC format, an integration team configures Transformer components that perform each conversion step visually. The difference from custom code is: Transformer logic is visible in the platform, editable by anyone with platform training, version-controlled, and does not require a developer to read or update when business logic changes.

Integration Platform-ipaas-slider-right
What are the most common types of data transformation needed in e-commerce integration?

The most common transformation types are: field mapping (renaming fields from source naming conventions to destination naming conventions), value conversion (converting status codes, country codes, currency values, date formats between systems), data filtering (removing records that should not reach the destination, such as cancelled orders from an order-to-fulfillment flow), data enrichment (adding fields from a lookup table or a third-party API call before the record reaches the destination), and data aggregation (combining multiple source records into a single destination record, such as combining multiple order lines into a single invoice).

Integration Platform-ipaas-slider-right
How does the Alumio Transformer handle complex transformation scenarios?

For complex scenarios beyond standard field mapping and value conversion, Alumio provides a Code Transformer component that allows custom PHP logic to be written and executed within a Route. The Code Transformer is used for edge cases that cannot be expressed through preconfigured components: complex conditional logic, custom validation rules, or proprietary format parsing. Unlike a fully custom integration, the Code Transformer operates within Alumio's platform infrastructure (benefiting from the same monitoring, logging, and deployment management) while providing the flexibility of custom code for the specific component that requires it.

Integration Platform-ipaas-slider-right
What happens when transformation logic needs to change after an integration is live?

Because Alumio Transformer logic is configured rather than custom-coded, changing transformation logic after go-live means updating the Transformer's configuration in the platform rather than editing and redeploying code. Changes can be tested in a sandbox or UAT environment before being applied to production, and Alumio's version control per Route preserves previous configurations if a rollback is needed. This makes it significantly faster and lower-risk to evolve transformation logic as business requirements change: a critical advantage in e-commerce environments where pricing, product, and order data requirements change frequently.

Integration Platform-ipaas-slider-right
How does mastering data transformation accelerate integration project delivery?

Mastering data transformation accelerates integration project delivery by compressing the most effort-intensive phase of integration projects: the data mapping work where source and destination field structures are reconciled. Teams with strong Transformer expertise can move through the mapping phase faster, recognize reusable patterns from previous projects, and apply consistent transformation approaches across multiple Routes in the same project. Alumio's Transformer library also grows with each project: transformation patterns built for one use case (SAP IDOC to JSON, Akeneo product structure to Shopify product API) become reusable components for subsequent projects with similar requirements.

Get a free assessment of your integration needs

Laptop screen displaying the Alumio iPaaS dashboard, alongside pop-up windows for generating cron expressions, selecting labels and route overview.