Thanks David, Sorry I attached a version of the neo4j.conf file that had only had the Upgrade line un-commented. I did uncomment this in subsequent endeavors.
Ok, tears of joy here, but not without more trial and tribulation, such is life. Here's the story...
I set up everything as you described in your video, but ran into this error (first 1/2 of pic below) when I tried to start with neo4j console...
Solution
This PowerShell? issue is likely unrelated to my Migration issue.
...
...
After employing the fix from stackoverflow, I ran neo4j console again, but saw no Migration Steps 1-6. So I turned to the debug.log file (which proved quite helpful).
In the log file I received this warning...
2020-02-11 21:58:05.558+0000 WARN [o.n.k.d.Database] [graph] Exception occurred while starting the database. Trying to stop already started components. The database is not cleanly shutdown. The database needs recovery, in order to recover the database, please run the old version of the database on this store.
org.neo4j.kernel.impl.storemigration.StoreUpgrader$DatabaseNotCleanlyShutDownException: The database is not cleanly shutdown. The database needs recovery, in order to recover the database, please run the old version of the database on this store.
So I Googled neo4j clean shutdowns and came across this info...
Solution
I did as the solution suggested and deleted 2 neostore.transaction.db.* files.
For the record, I had been using a database that runs on my local, hence the 'dirty' shutdown (since there doesn't seem to be a way to run neo4j stop when running neo4j console) So I ran neo4j stop against a test database thinking these neostore.transaction files would be gone. They were not, so still left wondering what a cleanshut down is and how to avoid this pitfall in the future.
...
...
I ran neo4j console again and received Migration 1-6 Joy! as seen here...
However, my labels and relationships were still not showing in localhost:7474/browser. So I turned to the log file again and found another warning that suggested I add a line to my conf file...
2020-02-11 22:11:27.552+0000 WARN [o.n.k.d.Database] [graph] Exception occurred while starting the database. Trying to stop already started components. Component 'org.neo4j.kernel.recovery.Recovery$MissingTransactionLogsCheck@7f12094d' failed to initialize. Please see the attached cause exception "Transaction logs are missing and recovery is not possible. To force the database to start anyway, you can specify 'dbms.recovery.fail_on_missing_files=false'. This will create new transaction log and will update database metadata accordingly. Doing this means your database integrity might be compromised, please consider restoring from a consistent backup instead.".
org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.recovery.Recovery$MissingTransactionLogsCheck@7f12094d' failed to initialize. Please see the attached cause exception "Transaction logs are missing and recovery is not possible. To force the database to start anyway, you can specify 'dbms.recovery.fail_on_missing_files=false'. This will create new transaction log and will update database metadata accordingly. Doing this means your database integrity might be compromised, please consider restoring from a consistent backup instead.".
I added dbms.recovery.fail_on_missing_files=false to the conf file, ran neo4j console, and my database migration APPEARS to be successful, meaning I can run cypher queries and see labels, relationships, and properties from my 3.5 data in the new neo4j 4.0.
...
...
That said, I'm hoping maybe you can confirm that what appears to be a successful migration actually is? Thank you so much for sticking with me and for providing the very helpful video. I seemed to have found other 'anomalies' that couldn't possibly be accounted for.
Many Thanks!
Keith