Entity Framework 7 scaffolding with original name

help you fix your problem I've not used the DbContext generator, but have had similar issues with the POCO Generator. Assuming that the solution is similar:
Modify the T4 template that creates the entity classes to add an extra attribute to the class:

[MetadataType(typeof(CustomerMetaData))]

public class CustomerMetaData
{

    [StringLength(150, ErrorMessage="Maximum length is 150 characters.")]
    [Required(ErrorMessage="CustomerName is required.")]
    public virtual string CustomerName
    {
        get;
        set;
    }
    public virtual Nullable<int> Type
    {
        get;
        set;

    }

    // ... etc ...
}

should help you out Thought this could use some expanding :) As mentioned above ASP.NET MVC 4 scaffolding does not support EF6 or higher. This means that an older EF, compatible with MVC 4 will have to be installed. To do this:
Open the Package Manager Console: select TOOLS -> Library Package Manager -> Package Manager Console

I hope this helps . I have: , When you query the Regions, Include Muscles as well.

return db.Regions.Include(s=>s.Muscles)

Hope this helps You can use DbContextWriter & EntityTypeWriter to customize scaffold output.
In newer versions of entity core writers renamed: DBContextWriter ==>> CSharpDbContextGenerator EntityTypeWriter ==>> CSharpEntityTypeGenerator

//HERE YOU CAN CHANGE THE WAY TYPES ARE GENERATED AND YOU CAN ADD INTERFACE OR BASE CLASS AS PARENT.
public class CustomEntitiyTypeWriter : EntityTypeWriter
{
    public CustomEntitiyTypeWriter([NotNull] CSharpUtilities cSharpUtilities)
        : base(cSharpUtilities)
    { }

    // Write Code returns generated code for class and you can raplec it with your base class
    public override string WriteCode([NotNull] EntityConfiguration entityConfiguration)
    {
        var classStr = base.WriteCode(entityConfiguration);

        var defaultStr = "public partial class " + entityConfiguration.EntityType.Name;
        var baseStr = "public partial class " + entityConfiguration.EntityType.Name + " : EntityBase";

        classStr = classStr.Replace(defaultStr, baseStr);

        return classStr;
    }      
}

public static void ConfigureDesignTimeServices(IServiceCollection services)
           => services.AddSingleton<EntityTypeWriter, CustomEntitiyTypeWriter>();

Does that help The safe way to upgrade production DB is to break it up in multiple steps:
Add new Market entity and attach it to Promotion entity without dropping the existing column EF will generate you a migration - CREATE TABLE + ADD FOREIGN KEY statements Make your code to update/insert/select new values from both Market table and Market column preferring Market table You deploy this. Now, you've got both old column with data and new table out there, being in sync for the new data. Write a data migration, which will copy old values from Market column to Market table. Run it. Now you've got your data moved to the new Market table and new data sitting in Market table Update your code to stop using old Market column. Deploy the change Remove Market column from you entity. EF will generate migration where column will be dropped. Deploy this. You now have your data and schema migrated