Migration from Magento 1 to Magento 2

Below are examples of scripts, which may be used for transferring data from Mirasvit RMA for Magento 1 to Mirasvit RMA for Magento 2.

To use scripts you need a help of PHP developer. Scripts may contain bugs and may not transfer all necessary data. So you may need to fit them for your needs. Migration service is not a part of our support service. If you need a help of our team, you'll need to buy a migration service. Click on the names of scripts below to download:

• mirasvit_rma_m1_export.php - script for exporting RMA data to XML file.
• mirasvit_rma_m2_import.php - script for importing RMA data from XML file.

How to perform Migration

Follow these steps to correctly perform migration:

1. Run standard Magento 2 migration, and make sure, that customers and orders were transferred from your M1 store to M2;
2. Make sure, that RMA for Magento 2 is installed on your M2 store.
3. Place mirasvit_rma_m1_export.php to the root of your M1 store, and run it either:
   • From browser by opening URL http://store_m1.com/mirasvit_rma_m1_export.php, or
   • From SSH/Console: navigate to your store's root and run command php -f mirasvit_rma_m1_export.php
4. If script returned success, file rma_export.xml will be created at the root of the store, with all your data. Transfer it to the root of your M2 store;
5. Place mirasvit_rma_m2_import.php to the root of your M2 store, and run it either:
   • From browser by opening URL http://store_m1.com/mirasvit_rma_m2_import.php, or
   • From SSH/Console: navigate to your store's root and run command php -f mirasvit_rma_m2_import.php
6. Check migrated data. 7, If there was some RMA skipped due to missing customers, their emails will be listed in missing-rma-customers.log file, at the root of the store. Create (or transfer) that customers and repeat step 5.
7. When migration is completed, remove both migration scripts.

Troubleshooting

Crush on timeout or exceeding available memory.

This error appears due to large quantities of data.

Solution:

Just restart import script by reloading browser page. It will skip previously uploaded data, and proceed from the last unprocessed record.

Crush with PHP Fatal Error during export

Typically this issue can appear, when you migrate from very old RMA for Magento 2, which has different table structure, or your store has old version of offline RMA.

Solution:

Open mirasvit_rma_m1_export.php file, and remove code block, marked with // 0.6. Offline Orders. This should be enough for most cases.

If script crushed even after custom fix above, contact Mirasvit Support.