cancel
Showing results for 
Search instead for 
Did you mean: 

Migration from 1.9.4.4 to 2.3.5

SOLVED
Highlighted

Migration from 1.9.4.4 to 2.3.5

Hi,

I have done a clean migration from 1944 to 235 using the data migration tool.

The settings-migration is done, 100% no errors.

The data-migration is giving this error:

[2020-05-04 12:30:08][INFO][mode: data][stage: data migration][step: EAV Step]: started
42% [============>---------------] Remaining Time: 1 sec
In Mysql.php line 182:

  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '10-design' for key 'EAV_ATTRIBUTE_GROUP_ATTR
  IBUTE_SET_ID_ATTRIBUTE_GROUP_CODE'

As I have said, this is the first migration, thus a clean destination database.

Who can help me?

Thx

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

Hi @dakota259 ,

 

Can you please do the migration with below steps:

 

1. if you have taken the backup of fresh Magento 2 database. Replace that Database with your existing instance of magento 2 database.

2. Try to migrate data with below command.

php bin/magento -a migrate:data path_to_config.xml

 

If you still face issues in the data migration. Please go through below link to tackle the errors occurring while migration.

https://www.goivvy.com/blog/magento-2-migration

 

------------------------------------

Problem solved? Give Kudo and Click Accept as Solution!

View solution in original post

5 REPLIES 5
Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

Hi @dakota259 ,

 

There is duplicate entry in your magento 1 database table eav_attribute_group

Please follow below steps:

1. In your Magento 1 database table eav_attribute_group 

2. search for attribute_group_code = design and check how many entry is there for this attribute_group_code.

3. If there is 2 entries for "design" try to delete one entry and start the migration again.

 

Error occurs because eav_attribute_group table want attribute_set_id and attribute_group_code must have unique entry.

 

Thanks!

Problem solved? Give Kudos and Click Accept as Solution!

Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

Hi,

Thanx for your reply. There are 9 records.

Image1.jpg

Do I have to remove 8 records?

Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

Hello @dakota259 

 

You can use  php bin/magento -r migrate:data path_to_config.xml  -vvv or if your doing in fresh db then run php bin/magento -a migrate:data path_to_config.xml  -vvv for more detail to check error. -vvv use for detail error.

 

Run below queries to check entries in M1 database(please take DB backup):

mysql> SELECT * FROM eav_entity_attribute WHERE attribute_group_id NOT IN (SELECT attribute_group_id FROM eav_attribute_group);


mysql> SELECT * FROM catalog_eav_attribute WHERE attribute_id NOT IN (SELECT attribute_id FROM eav_attribute);


mysql> SELECT * FROM catalog_eav_attribute WHERE attribute_id NOT IN (SELECT attribute_id FROM eav_attribute);
 
If any records exists then just run below shared queries:
-- Fix SOURCE DB Orphaned things....
DELETE FROM eav_attribute_set WHERE entity_type_id NOT IN (SELECT entity_type_id FROM eav_entity_type);
DELETE FROM eav_entity_attribute WHERE attribute_group_id NOT IN (SELECT attribute_group_id FROM eav_attribute_group);
DELETE FROM catalog_eav_attribute WHERE attribute_id NOT IN (SELECT attribute_id FROM eav_attribute);

 If you will find any specific table error then just rename that table and try it again in fresh db.

Problem solved? Click Kudos & Accept as Solution!
Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

No records were found with these queries.

With php bin/magento -r migrate:data path_to_config.xml  -vvv :

Reset the current position of migration to start from the beginning

[2020-05-04 15:07:32][INFO][mode: data][stage: integrity check][step: Data Integrity Step]: started
[2020-05-04 15:07:39][INFO][mode: data][stage: integrity check][step: EAV Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:39][ERROR]: Incompatibility in data. Source document: eav_attribute. Field: source_model. Error: Class shippingmanager/carrier_system_config_source_method is not mapped in record attribute_id=139
[2020-05-04 15:07:39][INFO][mode: data][stage: integrity check][step: Customer Attributes Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:40][INFO][mode: data][stage: integrity check][step: Map Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][ERROR]: Source documents are not mapped: bpost_country,bpost_holidays,bpost_shipping_returnlabel,bpost_tablerates_clickcollect,bpost_tablerates_homedelivery,bpost_tablerates_international,bpost_tablerates_parcellocker,bpost_tablerates_pickuppoint,bpost_tablerates_pickuppointinternational,catalog_product_entity_varchar_kopie,catalog_product_entity_varchar_kopie_old,customgrid_grid,customgrid_grid_column,customgrid_grid_profile,customgrid_grid_role,customgrid_grid_user,customgrid_options_source,customgrid_options_source_model,customgrid_options_source_option,customgrid_role_profile,emagicone_mobassistantconnector_failed_login,emagicone_mobassistantconnector_sessions,imaclean,manageimage,manufacturer,mollie_methods,mollie_payments,orderrequest,shipment_carriers,sm_products_filter
[2020-05-04 15:07:47][ERROR]: Destination documents are not mapped: pma__bookmark,pma__central_columns,pma__column_info,pma__designer_settings,pma__export_templates,pma__favorite,pma__history,pma__navigationhiding,pma__pdf_pages,pma__recent,pma__relation,pma__savedsearches,pma__table_coords,pma__table_info,pma__table_uiprefs,pma__tracking,pma__userconfig,pma__usergroups,pma__users
[2020-05-04 15:07:47][ERROR]: Source fields are not mapped. Document: sales_flat_order. Fields: bpost_label_exported,bpost_label_exists,bpost_drop_date,bpost_status,bpost_return_label_exists,bpost_reference,bpost_pickuplocation_id,bpost_notification_sms,bpost_notification_email,bpost_reduced_mobility,bpost_disable_saturday_delivery,bpost_delivery_date
[2020-05-04 15:07:47][ERROR]: Source fields are not mapped. Document: sales_flat_quote. Fields: bpost_drop_date,bpost_pickuplocation_id,bpost_notification_sms,bpost_notification_email,bpost_reduced_mobility,bpost_disable_saturday_delivery,bpost_delivery_date,bpost_saturday_cost_applied
[2020-05-04 15:07:47][ERROR]: Source fields are not mapped. Document: sales_flat_shipment. Fields: bpost_label_exported,bpost_label_path,bpost_tracking_url,bpost_status,bpost_shipment_automated,bpost_return_barcode
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: Url Rewrite Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: Log Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: Ratings Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: ConfigurablePrices step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: OrderGrids Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: Tier Price Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: SalesIncrement Step]: started
100% [============================] Remaining Time: < 1 sec
[2020-05-04 15:07:47][INFO][mode: data][stage: integrity check][step: Inventory Step]: started
100% [============================] Remaining Time: < 1 sec
[NOTICE]: You can use --auto or -a option to ignore not mapped differences between source and destination to continue migration
In Data.php line 97:

  [Migration\Exception]
  Integrity Check failed


Exception trace:
  at D:\Tools\xampp\htdocs\magento2\vendor\magento\data-migration-tool\src\Migration\Mode\Data.php:97
 Migration\Mode\Data->runIntegrity() at D:\Tools\xampp\htdocs\magento2\vendor\magento\data-migration-tool\src\Migration\Mode\Data.php:62
 Migration\Mode\Data->run() at D:\Tools\xampp\htdocs\magento2\vendor\magento\data-migration-tool\src\Migration\Console\MigrateDataCommand.php:59
 Migration\Console\MigrateDataCommand->execute() at D:\Tools\xampp\htdocs\magento2\vendor\symfony\console\Command\Command.php:255
 Symfony\Component\Console\Command\Command->run() at D:\Tools\xampp\htdocs\magento2\vendor\magento\framework\Interception\Interceptor.php:58
 Migration\Console\MigrateDataCommand\Interceptor->___callParent() at D:\Tools\xampp\htdocs\magento2\vendor\magento\framework\Interception\Interceptor.php:138
 Migration\Console\MigrateDataCommand\Interceptor->Magento\Framework\Interception\{closure}() at D:\Tools\xampp\htdocs\magento2\vendor\magento\framework\Interception\Interceptor.php:153
 Migration\Console\MigrateDataCommand\Interceptor->___callPlugins() at D:\Tools\xampp\htdocs\magento2\generated\code\Migration\Console\MigrateDataCommand\Interceptor.php:104
 Migration\Console\MigrateDataCommand\Interceptor->run() at D:\Tools\xampp\htdocs\magento2\vendor\symfony\console\Application.php:1001
 Symfony\Component\Console\Application->doRunCommand() at D:\Tools\xampp\htdocs\magento2\vendor\symfony\console\Application.php:271
 Symfony\Component\Console\Application->doRun() at D:\Tools\xampp\htdocs\magento2\vendor\magento\framework\Console\Cli.php:115
 Magento\Framework\Console\Cli->doRun() at D:\Tools\xampp\htdocs\magento2\vendor\symfony\console\Application.php:147
 Symfony\Component\Console\Application->run() at D:\Tools\xampp\htdocs\magento2\bin\magento:23
Highlighted

Re: Migration from 1.9.4.4 to 2.3.5

Hi @dakota259 ,

 

Can you please do the migration with below steps:

 

1. if you have taken the backup of fresh Magento 2 database. Replace that Database with your existing instance of magento 2 database.

2. Try to migrate data with below command.

php bin/magento -a migrate:data path_to_config.xml

 

If you still face issues in the data migration. Please go through below link to tackle the errors occurring while migration.

https://www.goivvy.com/blog/magento-2-migration

 

------------------------------------

Problem solved? Give Kudo and Click Accept as Solution!

View solution in original post