Hi Dipak,

When you say that you have followed all the steps - did you switch all ApplicationUser usages on startup.cs (or whatever file you have your OWIN StartUp) to your CustomUser?

This is easy for you to test on your local machine:

• create new Alloy MVC site (with or without search)
• create your custom application user class
• modify the startup.cs and replace all usages of 'ApplicationUser' with your custom app user type
• run Alloy
  • you create the initial user
• look at the table 'AspNetUsers' and you can see that your custom property / properties are here

Was the site first created using Episervers ApplicationUser and then you decided to switch to your own custom implementation? If yes, then that is why you don't see any changes in your AspNetUsers table. You need to run migrations and it isn't straight forward like just running enable-migrations and pointing to Episerver ASP.NET identity type and assembly (like you would normally run migrations in an ASP.NET EF project).

So if you can start clean with the user database, that is your fastest option or see this blog post about running the migrations programmatically. I'm not sure if that will either work as you are changing the actual user type too.