Migrate 1.9.5 to 4.1.1

Is there documentation to migrate from a very old version 1.9.5 to latest? I was trying to use liquibase-maven-plugin 4.1.1 on 1.9.5 databasechangelog table. I added all new columns but it is giving me the following error

Caused by: org.apache.maven.plugin.MojoExecutionException:
Error setting up or running Liquibase:
java.lang.NullPointerException
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$null$0(AbstractLiquibaseMojo.java:449)
at liquibase.Scope.lambda$child$0(Scope.java:160)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:159)
at liquibase.Scope.child(Scope.java:138)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$execute$1(AbstractLiquibaseMojo.java:372)
at liquibase.Scope.lambda$child$0(Scope.java:160)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:159)
at liquibase.Scope.child(Scope.java:138)
at liquibase.Scope.child(Scope.java:222)
at liquibase.Scope.child(Scope.java:226)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute(AbstractLiquibaseMojo.java:306)
… 21 more
Caused by: liquibase.exception.LiquibaseException: java.lang.NullPointerException
at liquibase.Liquibase.runInScope(Liquibase.java:2282)
at liquibase.Liquibase.update(Liquibase.java:215)
at liquibase.Liquibase$1.run(Liquibase.java:394)
at liquibase.Scope.lambda$child$0(Scope.java:160)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:159)
at liquibase.Scope.child(Scope.java:138)
at liquibase.Liquibase.runInScope(Liquibase.java:2277)
at liquibase.Liquibase.update(Liquibase.java:379)
at liquibase.Liquibase.update(Liquibase.java:371)
at liquibase.Liquibase.update(Liquibase.java:666)
at org.liquibase.maven.plugins.LiquibaseUpdateSQL.doUpdate(LiquibaseUpdateSQL.java:51)
at org.liquibase.maven.plugins.AbstractLiquibaseUpdateMojo.performLiquibaseTask(AbstractLiquibaseUpdateMojo.java:30)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$null$0(AbstractLiquibaseMojo.java:446)
… 33 more
Caused by: java.lang.NullPointerException
at liquibase.changelog.StandardChangeLogHistoryService.getRanChangeSets(StandardChangeLogHistoryService.java:329)
at liquibase.changelog.AbstractChangeLogHistoryService.upgradeChecksums(AbstractChangeLogHistoryService.java:65)
at liquibase.changelog.StandardChangeLogHistoryService.upgradeChecksums(StandardChangeLogHistoryService.java:292)
at liquibase.Liquibase.checkLiquibaseTables(Liquibase.java:1788)
at liquibase.Liquibase.lambda$update$1(Liquibase.java:232)
at liquibase.Scope.lambda$child$0(Scope.java:160)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:159)
at liquibase.Scope.child(Scope.java:138)
at liquibase.Liquibase.runInScope(Liquibase.java:2277)
… 46 more

I found from the liquibase source code that it is reading the value of ORDEREXECUTED and EXECTYPE so I have set those values as -1 and ‘EXECUTED’

update databasechangelog
set ORDEREXECUTED = -1, exectype=‘EXECUTED’

It seems to be working but it just keep on showing the following WARNING

And it generates a lots of update statements to MD5SUM to existing changesets.

Is it the way to migrate to 4.1.1?

[WARNING] Cannot create filesystem for url file:/C:/projects/workspace/myproject/target/classes: C:\projects\workspace\myproject\target\classes
java.nio.file.FileSystemNotFoundException: C:\projects\workspace\IntelliJ\myproject\target\classes
at com.sun.nio.zipfs.ZipFileSystem. (ZipFileSystem.java:120)
at com.sun.nio.zipfs.ZipFileSystemProvider.newFileSystem (ZipFileSystemProvider.java:139)
at java.nio.file.FileSystems.newFileSystem (FileSystems.java:390)
at liquibase.resource.ClassLoaderResourceAccessor.loadRootPaths (ClassLoaderResourceAccessor.java:63)
at liquibase.resource.ClassLoaderResourceAccessor.loadRootPaths (ClassLoaderResourceAccessor.java:79)
at liquibase.resource.ClassLoaderResourceAccessor.init (ClassLoaderResourceAccessor.java:47)
at liquibase.resource.ClassLoaderResourceAccessor.openStreams (ClassLoaderResourceAccessor.java:94)
at org.liquibase.maven.plugins.MavenResourceAccessor.openStreams (MavenResourceAccessor.java:21)
at liquibase.resource.CompositeResourceAccessor.openStreams (CompositeResourceAccessor.java:33)
at liquibase.resource.AbstractResourceAccessor.openStream (AbstractResourceAccessor.java:17)
at liquibase.parser.core.xml.XMLChangeLogSAXParser.parseToNode (XMLChangeLogSAXParser.java:51)
at liquibase.parser.core.xml.AbstractChangeLogParser.parse (AbstractChangeLogParser.java:15)
at liquibase.Liquibase.getDatabaseChangeLog (Liquibase.java:337)
at liquibase.Liquibase.lambda$update$1 (Liquibase.java:229)
at liquibase.Scope.lambda$child$0 (Scope.java:160)
at liquibase.Scope.child (Scope.java:169)
at liquibase.Scope.child (Scope.java:159)
at liquibase.Scope.child (Scope.java:138)
at liquibase.Liquibase.runInScope (Liquibase.java:2277)
at liquibase.Liquibase.update (Liquibase.java:215)
at liquibase.Liquibase$1.run (Liquibase.java:394)
at liquibase.Scope.lambda$child$0 (Scope.java:160)
at liquibase.Scope.child (Scope.java:169)
at liquibase.Scope.child (Scope.java:159)
at liquibase.Scope.child (Scope.java:138)
at liquibase.Liquibase.runInScope (Liquibase.java:2277)
at liquibase.Liquibase.update (Liquibase.java:379)
at liquibase.Liquibase.update (Liquibase.java:371)
at liquibase.Liquibase.update (Liquibase.java:666)
at org.liquibase.maven.plugins.LiquibaseUpdateSQL.doUpdate (LiquibaseUpdateSQL.java:51)
at org.liquibase.maven.plugins.AbstractLiquibaseUpdateMojo.performLiquibaseTask (AbstractLiquibaseUpdateMojo.java:30)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$null$0 (AbstractLiquibaseMojo.java:446)
at liquibase.Scope.lambda$child$0 (Scope.java:160)
at liquibase.Scope.child (Scope.java:169)
at liquibase.Scope.child (Scope.java:159)
at liquibase.Scope.child (Scope.java:138)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.lambda$execute$1 (AbstractLiquibaseMojo.java:372)
at liquibase.Scope.lambda$child$0 (Scope.java:160)
at liquibase.Scope.child (Scope.java:169)
at liquibase.Scope.child (Scope.java:159)
at liquibase.Scope.child (Scope.java:138)
at liquibase.Scope.child (Scope.java:222)
at liquibase.Scope.child (Scope.java:226)
at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute (AbstractLiquibaseMojo.java:306)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
at org.codehaus.classworlds.Launcher.main (Launcher.java:47)

Hi @tom2011,

There has definitely been md5checksum changes, so that looks like you are on the right path. Honestly, if it were me, I would sign up for a Pro Trial and schedule a meeting with Support to at least validate your strategy:

Full disclosure I work for the company but, I think this is a pretty good play.

-Ronak