Notes on Synchronizing Databases

• When synchronizing databases, no information is removed from the Source database. It is only being added to the Destination database.
• Information that already exists in the Destination database will be updated to reflect what the Source database contains. (See note below for an exception)
• Synchronizing databases does not copy or transfer any Bids; only the Master Tables are affected. To transfer Bids from one database to another, follow the instructions in your product's User Guide for Copying and Pasting Bids.
• Synchronizing databases does not copy over the New Bid, M/U Cost Codes, or Lookup settings configured under Tools > Options. These must be configured manually for every database.
• Synchronizing database does copy over the General, Category Codes, and Folders settings configured under Tools > Options.
• For Quick Bid, synchronizing database does copy over the settings configured under Tools > Payroll Settings and Tools > Default Markups and Indirect Expenses.
• When synchronizing databases, all Master Tables or a combination of Tables can be synchronized (by default, all Master Tables are copied to the new database). You can adjust this before synchronizing.

Some companies keep a Master (template) Database and synchronize to this when creating new databases for each project, month, quarter, etc. - however they've chosen to organize their databases. This can save a great deal of time when setting up new databases and ensures every database contains the same settings and Master information.

For Contacts, let's say you enter "Michael Smith Company" as a Contact in your Source database and synchronize it with a Destination database. A Contact "Michael Smith Company" is created, as expected, in the Destination. Now, let's say you edit that Contact in your Source database, maybe the company's name changed to "MSmith Co.". When you synchronize your Source into your Destination database again, Quick Bid does not update the existing "Michael Smith Company" record, it creates a new Contact named "MSmith Co" and leaves the existing Contact untouched. This is done to preserve historical data/states of existing bids. If you want you users to have a fresh set of Contact, based off your Source, they should create new databases and then synchronize those to your Source database.