You really do not need to do an import for a new version of the software. You can do what I do. If a new version of your software requires a change to the structure of your database, you can create a small program which all it does is alter the structure of your end user's database. For example:
SqlExecute('ALTER TABLE company ADD COLUMN coPhone TEXT');
You can also create tables and even populate new tables through this program. Then when it comes time to distribute to your users, you send them the new version of your main program and in addition send them the small database upgrade program. Have your end users run the database upgrade program first. All this program does is change in place their database structure for the new version of your program. No import is necessary. When they run their new version of the program it will be accessing the new version of the database that is already populated.
If you use an install software for your users, you can have this database upgrade program automatically run during the install of your new main program. The user does not even know that it happened.
Optionally there is a PRAGMA instruction to check for the database version prior to the update. So that if the database is not the correct version, then you can take the appropriate steps to either update it or present an error message and not do the update.