As you move onto the new Microbizz architecture, it is possible for some modules to both have the new module and the old module at the same time. The cross-save system will ensure that data is synchronized between the two modules.

Turning on cross-save

When you turn on cross-save all data from the old module will be transferred into the new module. This is also true, if you disable cross-save and turn it on again later.

Therefore you should only turn on cross-save if there isn’t data in the new architecture that you want to keep.

After that all things you do in the old module will transfer into the new module and vice versa.

Turning off cross-save

If you turn off cross-save, data will not synchronize between the old and the new module anymore. The only way to get this functionality back, is to turn on crosssave again, which will delete all data in the new module and transfer the data from the old module.

Speed considerations

When cross-save is turned on, the system needs to save in both the new and old architecture, so you will this experiences the delays from the old architecture. Therefore cross-save should be turned off when evaluating the new module for speed purposesCross-save is automatically enabled/disabled for the various objects depending on which modules are enabled on your system.

You may reset the cross-saving, this will delete all the new objects and then recreate new objects feom the old objects. Don't do this unless there is a good reason.