Unable to upgrade from Umbraco 6.0.7 to 7.4.0
<p>I need to upgrade one of our websites from Umbraco 6.0.7 to 7.4.0. I've updated the NuGet package and followed upgrade guides. I've replaced <code>umbraco</code>, <code>umbraco_client</code> and <code>config</code> folders to make sure there is no configuration incompatible with 7.4.0. </p>

<p>Unfortunately, the update wizard fails with this error message:</p>

<pre><code> 2016-02-16 20:57:13,838 [P6904/D3/T10] ERROR Umbraco.Core.DatabaseContext - Database configuration failed
Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: 'System.Dynamic.ExpandoObject' does not contain a definition for 'NodeId'
   at CallSite.Target(Closure , CallSite , Object )
   at System.Dynamic.UpdateDelegates.UpdateAndExecute1[T0,TRet](CallSite site, T0 arg0)
   at Umbraco.Core.Persistence.Migrations.Upgrades.TargetVersionSeven.UpdateRelatedLinksData.&lt;UpdateRelatedLinksDataDo&gt;b__15(Object x)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Linq.Enumerable.&lt;DistinctIterator&gt;d__63`1.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Umbraco.Core.Persistence.Migrations.Upgrades.TargetVersionSeven.UpdateRelatedLinksData.UpdateRelatedLinksDataDo(Database database)
   at Umbraco.Core.Persistence.Migrations.Syntax.Execute.Expressions.ExecuteCodeStatementExpression.Process(Database database)
   at Umbraco.Core.Persistence.Migrations.MigrationRunner.ExecuteMigrations(IMigrationContext context, Database database)
   at Umbraco.Core.Persistence.Migrations.MigrationRunner.Execute(Database database, DatabaseProviders databaseProvider, Boolean isUpgrade)
   at Umbraco.Core.Persistence.Migrations.MigrationRunner.Execute(Database database, Boolean isUpgrade)
   at Umbraco.Core.DatabaseContext.UpgradeSchemaAndData(IMigrationEntryService migrationEntryService)
</code></pre>

<p>It seems that <code>UpdateRelatedLinksData</code> upgrade step expects different data / schema. How to fix this? Are there any manual changes to database required?</p>