Upgrading from Churchinfo 1.3.1

[DangerMoused]

My church has been using churchinfo for a while and I just discovered that churchcrm is a thing. I'd like to migrate us churchcrm. I attempted the side by side upgrade, but was unsuccessful. We are on the current version of Churchinfo which is 1.3.1, and is main point of difference I can see between the directions and our install.

I deployed churchcrm and everything appeared to work correctly. When I restored the unencrypted backup from churchinfo, churchcrm no longer loads. I'm a decent troubleshooter, but my skillset is more sysadmin than developer.

Our setup is:
Shared hosting
PHP 8.2
Cpanel - though I did uploads and some configuration through shell
Linux version(uname -a):
Linux redacted.server.com 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 x86_64 x86_64 GNU/Linux
Co-hosted mysql db
File permissions are correct

app.log:

[2024-02-27T19:17:31.480327-07:00] defaultLogger.INFO: Signature file found at: /home1/username/public_html/ccrm/setup/..//signatures.json [] {"url":"/setup/SystemIntegrityCheck","remote_ip":"111.222.333.444","correlation_id":"65de97bb7544d"}
[2024-02-27T19:18:51.373676-07:00] defaultLogger.INFO: Signature file found at: /home1/username/public_html/ccrm/setup/..//signatures.json [] {"url":"/setup/SystemIntegrityCheck","remote_ip":"111.111.111.111","correlation_id":"65de980b5b3b2"}
[2024-02-27T19:18:54.840997-07:00] defaultLogger.INFO: Signature file found at: /home1/username/public_html/ccrm/setup/..//signatures.json [] {"url":"/setup/SystemIntegrityCheck","remote_ip":"111.111.111.111","correlation_id":"65de980ecd52b"}
[2024-02-27T19:20:10.077196-07:00] defaultLogger.INFO: Starting application integrity check [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de985a04cb0"}
[2024-02-27T19:20:10.077968-07:00] defaultLogger.INFO: Signature file found at: /home1/username/public_html/ccrm/signatures.json [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de985a04cb0"}
[2024-02-27T19:20:10.412025-07:00] defaultLogger.INFO: Application integrity check passed [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de985a04cb0"}
[2024-02-27T19:25:15.633947-07:00] defaultLogger.INFO: Beginning to process incoming archive for restoration [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:25:15.640968-07:00] defaultLogger.INFO: Restore job created; ready to execute [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:25:15.641032-07:00] defaultLogger.INFO: Executing restore job [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:25:15.641068-07:00] defaultLogger.INFO: Decrypting file: /home1/username/public_html/ccrm/tmp_attach/ChurchCRMBackups/ChurchInfo-Backup-20240227-212449.sql [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:25:15.643308-07:00] defaultLogger.INFO: Bad version header; this file probably wasn't encrypted [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:25:17.291192-07:00] defaultLogger.INFO: Finished executing restore job.  Cleaning out temp folder. [] {"url":"/api/database/restore","remote_ip":"111.222.333.444","correlation_id":"65de998b9ac63"}
[2024-02-27T19:45:11.178606-07:00] defaultLogger.INFO: Installing ChurchCRM Schema [] {"url":"/","remote_ip":"111.222.333.444","correlation_id":"65de9e372b9b6"}
[2024-02-27T19:45:11.667227-07:00] defaultLogger.INFO: Installed ChurchCRM Schema version: 5.5.0 [] {"url":"/","remote_ip":"111.222.333.444","correlation_id":"65de9e372b9b6"}
[2024-02-27T19:45:13.508830-07:00] defaultLogger.INFO: Starting application integrity check [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de9e396d7d6"}
[2024-02-27T19:45:13.508975-07:00] defaultLogger.INFO: Signature file found at: /home1/username/public_html/ccrm/signatures.json [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de9e396d7d6"}
[2024-02-27T19:45:13.864153-07:00] defaultLogger.INFO: Application integrity check passed [] {"url":"/api/background/timerjobs","remote_ip":"111.222.333.444","correlation_id":"65de9e396d7d6"}

Likely relevant entry from the php.log:

[27-Feb-2024 21:38:27 America/New_York] PHP Fatal error:  Uncaught PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'ver_update_end' in 'order clause' in /home1/username/public_html/ccrm/vendor/propel/propel/src/Propel/Runtime/Connection/StatementWrapper.php:204
Stack trace:
#0 /home1/username/public_html/ccrm/vendor/propel/propel/src/Propel/Runtime/Connection/StatementWrapper.php(204): PDOStatement->execute(NULL)
#1 /home1/username/public_html/ccrm/ChurchCRM/Service/SystemService.php(47): Propel\Runtime\Connection\StatementWrapper->execute()
#2 /home1/username/public_html/ccrm/ChurchCRM/Bootstrapper.php(315): ChurchCRM\Service\SystemService::getDBVersion()
#3 /home1/username/public_html/ccrm/ChurchCRM/Bootstrapper.php(74): ChurchCRM\Bootstrapper::isDBCurrent()
#4 /home1/username/public_html/ccrm/Include/LoadConfigs.php(23): ChurchCRM\Bootstrapper::init('localhost', '3306', 'db_user', 'db_password', 'user', '', false, Array)
#5 /home1/username/public_html/ccrm/Include/Config.php(63): require_once('/home1/username...')
#6 /home1/username/public_html/ccrm/index.php(22): require_once('/home1/username...')
#7 {main}
  thrown in /home1/username/public_html/ccrm/vendor/propel/propel/src/Propel/Runtime/Connection/StatementWrapper.php on line 204

Any suggestions on what to try to get our data from churchinfo into churchcrm?

[DawoudIO]

Can you try the change in #6896 and just add 1.3.1 to the file and see if that work. I have no installed 1.3.1 so I don't know the diff

[DAcodedBEAT]

@DawoudIO the original author referenced https://church-web-crm.readthedocs.io/ but I don't think this is actively maintained. Is this owned by us?

[DangerMoused]

I added the 1.3.1 to the versions array in the upgrade.json and restored a backup from churchinfo. The same thing happens and I have the same errors in both the the php and the app log.

I logged into mysql and confirmed that the database did restore.

[DawoudIO]

ok let me see if I can do it myself

[DangerMoused]

If it would be helpful I deployed a new churchinfo 1.3.1 install, changed nothing but the admin password, then took a database backup. It does not restore correctly into ChurchCRM. I've attached the sample churchinfo 1.3.1 backup if you need a test to restore with.
ChurchInfo-Backup.zip

[DawoudIO]

thanks for the backup, there is a lot of old upgrade code that is not working, I'm making changes and testing now... should have it by the weekend

[DawoudIO]

ok #6896 is now working, once the following dev build is complete can you try upgrading and let me know if it works.

https://github.com/ChurchCRM/CRM/actions/runs/8206428511

[DangerMoused]

It appears to be working. After restoring I got the database upgrade required page, it ran, and I'm able to log in. I haven't encountered any other problems.

[DawoudIO]

Perfect welcome to the party

[DangerMoused]

Thanks for the help.

[DawoudIO]

https://github.com/ChurchCRM/CRM/actions/runs/8206428511/artifacts/1309978236

[gmhall506]

I eventually had success getting from ChurchInfo 1.3.1 to the latest release of ChurchCRM. It would seem to be mostly a database compatibility issue. The jump from 1.3 to 2.0 is the most significant leap.
My original plan was to do a step by step upgrade but no versions of ChurchCRM are available for download older than 5.0.
I was able to load on my server a backup of my 1.3 and with PHPMyAdmin run the upgrade scripts, in order, that I found in the ChurchCRM repository using tags to locate v. 2.0. I backed up that result, cleared the existing ChurchCRM database and uploaded to it. ChurchCRM then was able to successfully autorun the database upgrade process. All of those upgrade scripts (2.0 - 6.x) are included in the current ChurchCRM.
I hope that's of some help.