Yeah, that's a bit more complicated. I think Sage just tells you to make a backup, run a Data Verification and if all looks good, install over your old version and convert your data. If I am handling the conversion for one of my clients, I pull in a copy of their database into my office the night before a scheduled rollout. Restore it here, run three reports, run a Data Verification, clean up obsolete data, reindex the database, convert it, rerun the three reports and compare against the previous version, check on bill layouts and other trouble spots, then back it up for delivery and restore the next day. If it is coming from a REALLY old version, or having trouble converting, then I might do a stepped conversion where I only try to take it up a few versions at a time. If all goes well with that, the next day, we make a safe copy of their old Timeslips, install the new Timeslips (the new Firebird SQL will need to be loaded directly on the server), restore my backup and then let all the users into the pool. That way, we don't disturb what the firm has in place until we know the data will convert properly. It usually does, but it's nice to know in advance and not have everyone locked out of the data while it converts, the time for which can vary greatly. So my way, downtime is kept to a minimum.
↧
