The MageBridgeTM Configuration in the Joomla!TM backend allows you to easily switch from one Magento Website to another, by just selecting this other Website in a drop-down box. Also switching from one MagentoTM instance to another is nothing more than just entering the new API-details. But are there any caveats?
Caching
One caveat is surely caching. As soon as you switch MageBridge to another Magento storeview/website/instance, make sure all caches are freshed within Joomla!. It's also wise to refresh the cache in Magento.
Menu-Items and module configurations
Another thing to watchout for are store-specific configurations. For instance, if the new store has different URL keys, than certain Menu-Items and certain Joomla! modules might not be working anymore. You will need to walk through all Menu-Items and modules to make sure they are working correctly.
Users and customers
Last but surely not least are users. If you switch from one Magento instance to another, user-details might not be in sync: If MageBridge has created copies of Joomla! users in the Magento database or vice versa, suddenly there might be wrong links. Note that MageBridge does not use IDs to link a Magento customer to a Joomla! user, but just uses the common factor: The email-address.
We recommend switching to Magento stores with the same customer-database, or otherwise that you make a fresh start by removing all Joomla! users and/or Magento customers.
XML-RPC reset
Within the MageBridge Settings in the Magento backend, the XML-RPC host is also cached by MageBridge. If you switch to another Magento API, you will see that the old Magento API is still being mentioned. Just hit the button Reset XML-RPC. This will empty out the XML-RPC information. As soon as you access MageBridge (from within Joomla!) again, these XML-RPC settings will be reinitialized.
