AspDotNetStorefront to nopCommerce Shopping Cart Migration

If you are considering AspDotNetStorefront to nopCommerce Migration, then, you need to know some strategic and important differences between these platforms. Both of these are Asp.Net based Microsoft Technology and use MS SQL Server as backend. Both have various common features so after migration you do not feel in an entirely different world. Both AspDNSF and NOP are code ownership based solution i.e. not a hosted solution. If you are happy with your existing hosting for AspDotNetStorefront, then, you can host your nopCommerce site in that itself. nopCommerce is open source and almost negligible cost whereas for AspDotNetStorefront you have to buy a license and buy upgrades as well.

From the perspective of speed, nopCommerce is better in the sense that it has deftly used the Caching and used it extensively. So, you will find page load time faster than your AspDotNetStorefront based website.

Once you finalize to migrate, the first and most daunting task is planning DB Migration, planning structure and architecture of your products. Here, you need an expert consultant who can effectively guide you to configure your products and migrate the database from AspDNSF to nopCommerce. The Most Important and Critical Migration Aspects are discussed below:

  – You do not get Product Variants in nopCommerce. Here you need to use Attributes which require a skillful and neat planning for the longevity of your new website. For Products, there are two type of Attributes available; Product Attributes, Specification Attributes. You can configure different pricing based on the Product Attributes e.g. Color/size. Specification Attributes are the ones which do not impact pricing but are for cosmetic value only.

The Attributes part in in nopCommerce is one of the most versatile among other competitive eCommerce platforms. You can plan any sort of combinations, anyn number of specifications which e.g. for a jewellery store could be quite lengthy like Finish, Metal, Metal Color, No. of Stones, Stone Type, Center Stone, Side Stone Information, Color, Average Color, Width, Available Sizes etc. In AspDotNetStorefront, you were required to use an entirely different type of product i.e. Kit Product for the same. In simple product in aspdnsf, you only have two attributes i.e. Color and Size.

  – Aspdnsf stores the locale specific data in the same field e.g. if you are having a multilingual website, your Product Name in all 3 languages will be stored in a single field in ‘Name’ column in the table ‘Product’. It uses XML formatting to store it. While nopCommerce uses a separate table for storing the translations in a separate table named ‘LocalizedProperty’. In case of multi-lingual websites, it makes it one of the biggest table in the db as every entity’s translation is stored in this table.

It also makes the migration bit complex for the developer and it is also not easily handled by eCommerce migration tools.

Whether you wish us to port your existing design or only wish the database to be migrated, eCommerce migration experts at Matrid have tons of experience to make this migration smooth for you.