You can use data migration tools for that purpose.

Currently are 2 migration tools in IFS Cloud available:

• DMM (Data Migration Manager) in IFS Cloud 22R..., in IFS Cloud 21Rx it was called SDM (Smart Data Manager) → search for “Data Migration Manager” in the navigator
• “Old” data migration tool → search for “Data Migration” in the navigator

The recommendation is to use DMM.

In the IFS Academy is a training for DMM available which is called “Smart Data Manager Essentials” and is a good starting point to get familiar with this tool.

There is also some good documentation in the online documentation available.

If you’ve never worked with a data migration tool within IFS then I recommend to order a training for the methodology, the tools(s) and best practices → E.g. TAA3P

/Jens

I am using 22R1 and sharing my experience with Data Migration Manager with respect to Basic Data upload. You can upload Basic Data onto SDM like you do with any Master Data by creating Migration Object (not to use default Basic Data Migration Object) and you can move the record to deployment container and then deploy onto an environment and then bring back the record to Basic Data container by extracting Basic Data from the Environment (from Basic Data Container, you can deploy the record to other environments)

As feature available to extract basic data from output container by enabling ‘Basic Data Extraction’ field in target Table Definition, but you can’t enable the filed for a Basic Data table example “Company” as it company id field doesn’t have any reference and you can only enable where the field has reference.

This feature is to extract and approve Basic Data from Master and Transactional Data entities

Hope it helps

@Jens 

You mention 

If you’ve never worked with a data migration tool within IFS then I recommend to order a training for the methodology, the tools(s) and best practices → E.g. TAA3P

Where is TAA3P?  I couldn’t find anything in IFS Academy.

@jporter 

Hi,

this is a success service which can be order at IFS. Please reach out to your IFS partner success manager.

/Jens

The data can be migrated into IFS cloud using the following steps:

Export the data from the current system into a format that can be imported into IFS cloud, such as CSV or SQL.
Create a storage account in IFS cloud to store the data.
Use the IFS Cloud Data Import tool to upload the data into the storage account.
Configure the data import process, including mapping the data to the appropriate fields in IFS cloud.
Execute the import process, which may take some time depending on the size of the data.
Verify the data has been successfully imported into IFS cloud.

As Jens states, while we currently support both the Data Migration Manager and the older Data Migration Tool, we strongly recommend customers and partners use the Data Migration Manager. Other than corrections, no further investment is going to be made in the legacy Data Migration Tool. Conversely, we’re investing heavily in ensuring that the Data Migration Manager offers an optimal experience for migration projects. 

May this information useful for you. official website

Is there not a third option?:

Use Rest APIs and load data directly (with the proper business rules included in the Rest APIs). 

What would be bad about using that path?

@Andrew Lichey  Currently DMM falls short compared to MTK.  What can we expect to be improved/included in 23R1?

Hi @jporter ,

We’ve made a lot of investments in the DMM across 22R2 and 23R1. In 23R1, we’ve significantly improve performance, added the ability to fetch data in the pre-deployment process (which helps with key resolution, calculating values, and defaulting data based on complex logic).

We’ve got investments planned for the DMM in our roadmap over the next few years. Those include things like concatinating data from multiple source columns, enforcing and validating case, validating migration data against data in the target environment, and scheduled migration jobs, just as an example. The DMM IS our tool of choice for migrations, and where all of our new feature investments will be made.

When we’re able to, we’ll look to deprecate the Data Migration Tool. There are a few use cases it uniquely supports, so we won’t deprecate it this year, but we intend to get down to one product.

I’m not an expert on the Migration Toolkit. However, Eric Heinze is the product manager for our migration tools and I know he’s been looking into the MIgration Toolkit and has a sense of the relative strengths and weaknesses of the products. Please reach out to him. Thank you!