Answer
Usually yes, but an import is rarely just a matter of reading in columns. First, duplicates, empty mandatory fields, inconsistent date and number formats and contradictory meanings have to be identified. Often the same column means something different in different files – or several columns actually describe the same thing.
That is why a migration is divided into steps: data inventory, mapping to the new model, cleansing rules, test import, business review and final transfer. For important records, it should be documented where they come from and which transformation was applied. Not every historical helper column needs to go into the new system. Sometimes an unalterable archive makes more sense than an expensive full migration. schukai reviews the scope and quality of the data before a fixed price is set, because the real uncertainty often lies not in the import code but in the state of the source data.
---
As of 3 September 2026
Further reading
Related topic: Business applications and web software