During the Akeneo SaaS migration for Japan, product data will be cloned from Akeneo v6 Production to Akeneo SaaS Production. However, Akeneo v6 will continue to be used for daily business operations during the migration period, which means any updates made in v6 after the Phase 1 data clone starts must be carefully tracked and re-applied to SaaS later.

This guide provides tips for updating and managing delta data during the migration. Delta data refers to any product updates, new SKU/SKN combinations, or content changes made in Akeneo v6 after 24 August 2026, when Phase 1 begins. These changes need to be logged and reapplied in Akeneo SaaS during Phase 3: Delta Re-entry, from 7–11 September 2026, so that SaaS contains the latest business data before the SFCC sync and go-live.

As agreed, due to the complexity of the data, Carol has agreed to support the update of the delta product data in phase 2 and phase 3. Japan eCommerce team and other users only need to log the changes they have made in v6 and validate the data in SaaS.

Phase 1: The Akeneo Project Team starts cloning data from Akeneo v6 Production to Akeneo SaaS Production.

Phase 2: Carol receives access to Akeneo SaaS Production and begins data transformation, import profile setup, and other required preparation activities.

Phase 3: Carol continues entering the delta information into Akeneo SaaS Production.

Once the Japan eCommerce team receives access to Akeneo SaaS Production, they will validate the data entered by Carol and observe the system behavior.

Phase 4: Data is synchronized from Akeneo SaaS Production to SFCC.

Phase 5: Hypercare support begins.

During Phrase 1 and Phrase 2, each member of the Japan team can maintain a personal log sheet to record the SKUs they have updated. For example:

Having a shared log with unique sku so that someone can export from Akeneo v6 and import to Akeneo SaaS, for example:

For example, each SKU should appear only once in the log. If duplicate records exist, they will be highlighted in red, as shown below. Please remove the duplicate row so that only one record remains for each SKU.

Click here to access the sheet, there are two tabs, one is [phase1_2] for recording all the changes made within phrase 1 and 2. And [phase3] for recording the changes made within phase 3.

There are three types of data to be re-entered:

There are approximately 226 attributes that should be exported, highlighted in green below.

The remaining attributes either are not used or are system attributes updated by the daily AS400 import — for example, upc — and therefore do not need to be exported from Akeneo v6.

Carol will export the data from Akeneo v6 on the last day of Phase 2 and last day of Phase 3, then re-import it into Akeneo SaaS Production.

During Phase 4, since it takes place on Friday afternoon, each individual will need to maintain their updates in both Akeneo v6 Production and Akeneo SaaS Production by themselves.

Click here for the full list.

The date and time attributes (e.g., scheduled_publish_time-ja_JP) will be removed from Akeneo SaaS by the Akeneo Project Team during the cloning process, as they are custom attributes.

The date attribute (e.g., date_archived-ja_JP) can be cloned. However, for delta data, users need to perform the import using a tailored import process.

During Phase 2, Carol will first recreate the date/time attributes in Akeneo SaaS. By the end of Phase 2, she will import all the date and date time value.

On the last day of Phase 3, Carol will export the data from Akeneo v6, then re-import it into Akeneo SaaS Production.

During Phase 4, since it takes place on Friday afternoon, each individual will need to maintain their updates in both Akeneo v6 Production and Akeneo SaaS Production by themselves.

This information can be directly exported from v6

You cannot use the standard product_import profile. Instead, you should use the tailored date and time import profile, as it can accept the date/time format listed above.

Click here to access the sample file

3. Drag and drop the file in xlsx

4. Select 更新のみ

5. Click インポートを起動

6. Once it is completed you can see the message like this

7. The date and time is now imported.

For the product images, since the naming convention and the way how it stores the data is different (v6 in product attributes where SaaS in Asset), you cannot export from v6 for direct import.

Decision: After discussing with Carol, Japan eCommerce Team agreed to proceed with Option C. Carol will update the delta images based on the log provided by the team.

With this in mind, you can consider the following options

Option A: Save the ZIP Files First, Then Unzip and Rename at the End

Reference Only — Not the Agreed Method

For the ZIP files downloaded from PIE, each individual should save a copy to the shared SharePoint folder. JP_SaaS_delta_images

Within JP_SaaS_delta_images, the Japan team should handle the image preparation and upload as follows:

Note: Please pay close attention to the quality of work during the image preparation process. There may be cases where the same image file name appears in different ZIP files but actually refers to different images. These should be carefully checked to avoid overwriting or importing incorrect images.

Option B: Save the Unzipped and Renamed Files Directly

Reference Only — Not the Agreed Method

This is similar to Option A, but each individual user from the Japan team needs to first unzip the files and rename the images to _p* using Carol’s VBA tool before placing them into the JP_SaaS_delta_images folders.

Note: Please pay close attention to the quality of work during the image preparation process. Since the files will be unzipped and renamed before being saved into the shared folder, each individual user must ensure that the correct images are selected, renamed properly using Carol’s VBA tool, and placed into the correct folder without overwriting others’ work. Any incorrect file name, missing image, duplicated image, or overwritten file may cause issues during the upload to Akeneo SaaS Production.

Option C: Export from Akeneo v6 and Import into Akeneo SaaS — Most Reliable, but Technical

Agreed Method

It is considered the most reliable approach because the images are exported directly from Akeneo v6 and then prepared for import into Akeneo SaaS. However, it is also technical because the exported image files are not immediately ready for SaaS import.

After export, the images are organized in a nested folder structure by SKU and image position, and each file must be extracted, renamed according to the SaaS asset naming convention, consolidated into the correct folder, and validated before import. If the image volume is large, this process requires careful batch handling and file verification to avoid incorrect file names, missing images, duplicate files, or accidental overwriting. Therefore, this option may require technical support or someone familiar with bulk file processing and image preparation.

4. Select this and click エクスポート to continue.

5. Once it is ready you can download the archived files which contains the images

6. Each folder will store the images using the following structure:

sku/image_*/file.jpg

for example

For example, if a SKU #12345678 has 10 images, they will be listed as follows:

12345678/image_1/5678000A.jpg

12345678/image_2/5678000B.jpg

12345678/image_3/5678000C.jpg

12345678/image_4/5678000D.jpg

12345678/image_5/5678000E.jpg

12345678/image_6/5678000F.jpg

12345678/image_7/5678000G.jpg

12345678/image_8/5678000H.jpg

12345678/image_9/5678000I.jpg

12345678/image_10/5678000J.jpg

7. The user needs to rename all images according to the pie+p().jpg naming convention and place them into the same folder.

8. Import the renamed images into the SaaS asset family.