title: Migrating data in an database created with EF code first (devart connector) to EFCore code first (sqlite)
body: <p>The EFCore documentation is very specific on what to do, to migrated an EF based codebase to EFCore <a href="https://docs.microsoft.com/en-us/ef/efcore-and-ef6/porting/" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/ef/efcore-and-ef6/porting/</a> . However, I could not find advice on how to bring the data stored in an sqlite database from EF to EFCore.</p>
  <p>Beside the obvious approach to read from the old EF dbcontext and write to the new EFCore context, we are exploring the possiblity to configure EFCore (using the same model classes) to create the same database schema created by EF and then use the EFCore dbcontext to read the data.</p>
  <p>Is this approach the recommended way to migrate the data or continue accessing the data from the old schema?</p>
  <p>There appear to be multiple differences in the schema created by EF and EFCore troubling me. Some of them might be related to the fact that with EF we used Devart dotConnect Data Provider while with EFCore we use the database provider that comes with the EFCore project.</p>
  <p>This leads to different representations of Guid being declared as Guid in EF and TEXT in EFCore. Also the name generation for foreign keys appears to be different, while EF generated names like Property_Id for relationships EFCore seems to create PropertyId instead.</p>