Skip to content

Migration Types

Migration jobs can be divided on the way they migrate data. Each type may have different procedures for migrating data.

This type of migration jobs transfers data between the database and files. The data can be imported to a single database logical unit or to a data migration container table (IC Table). You can export the data from multiple logical units to a single file.

This type of migration jobs can be used to migrate data from one data source to another. The source can be a TABLE, VIEW, JOIN, DB LINK or UNION, while the destination can be a single or multiple logical units in the database.

This type of migration job can be used to migrate data between Microsoft Excel (using the IFS Excel Add-In) and the database. Data can be both queried from and saved into single or multiple logical units.

This type of migration jobs can be used to replicate data within an IFS Application instance. Internal Replication can be configured to replicate data between Sites and Companies in the same IFS Applications instance.

Use this type when you need to export/import migration jobs between IFS Application instances.

Note: Starting from the 24R1 release, we have introduced a time zone feature. When migrating data, if you need to convert migrated date values into a specific time zone,

follow these steps:

  1. Choose a Method: Select one of the methods available in TIME_SYS
  2. Set Default Value: Add the method as a default value in the source mapping. E.g. TIME_SYS.Convert_Utc_To_Server(INVOICE_DATE)

If you are working with CRM tables please check here.

During data migration involving entities which includes timestamps, timestamps are assumed to be aligned with the time zone as specified by the entity's TimestampTZRef property.

e.g. When the TimestampTZRef property is set to server, all timestamps belonging to that entity should be associated with the server's time zone, ensuring proper time zone alignment during the migration process.