What is copied

During the process, this data is copied from the source to the target database:

• UET definitions. Only the impacted schema changes are copied. If the source database has UET data that has not been impacted, it is not copied. The schema is impacted at the target if necessary. (For validation information, see Validations.)
• All multi-site tables except AccountAuthorization_mst, user_local_mst, and UserGroupMap_mst. If these three tables are not shared, then they are copied like any other multi-site table. If these tables are shared, they are processed like other user tables, based on the type of sharing being done (see below).
• All non-multi-site tables. Some tables require special processing:
  • Notes: Internal token numbers that overlap are renumbered. If the same note text exists in both the source and target databases, after the copy there are duplicate notes in the target.
  • Documents: Sequence numbers that overlap are renumbered.
  • Service schedules (see above for validation information)
  • Application Event System data:
    • New Event rows are copied from source to target
    • New EventMessageCategory are copied from source to target
    • New EventInitialState rows are copied from source to target
    • If anything is different in EventInitialVariables for an existing EventInitialState record, the state is renamed when it is copied to the target. For example, xxx becomes xxx2. The copied event handlers are also changed to use the new initial state name.
    • New EventInitialVariable are copied from source to target, as well as existing rows that required a newly renamed EventInitialState record.
  • Users and Groups: What is copied depends on the type of sharing, if any, currently being done between the source site and the target database:
    • No sharing of user tables between source and target: for tables where UserId is part of the unique key, copy the unique records; if duplicate user IDs exist, use the record from the target.
    • If all sites are on the same intranet, the source site is a subordinate site and the target database contains a master site: For tables where UserId is part of the unique key, copy the unique records; if duplicate user IDs exist, ignore the duplicates, remapping UserId during the process for comparison.
    • If all sites are on the same intranet, the source site is the master site, and the target database contains only subordinate sites: Drop the view in the target database, and copy the source table into the target database. For tables where UserId is part of the unique key, copy the unique records; if duplicate user IDs exist, ignore the duplicates, remapping UserId during the process for comparison.
    • If all sites are on the same intranet, the source site is a subordinate site, and the target database contains only subordinates sites: For tables where UserId is part of the unique key, copy the unique records; if duplicate user IDs exist, ignore the duplicates, remapping UserId during the process for comparison.
  • UserPasswordHistory: If users are shared, this table is always shared. If users are not shared, and the user already exists in the target database, the history is not copied. If the user does not exist in the target database, the history is copied.
• Replication document metadata is copied from the source to the target only if the target database does not currently contain any replication document metadata.
• Custom (non-SyteLine) tables, either multi-site or not multi-site. To copy a non-multi-site custom table, the copy process requires a unique constraint on the table, and it tries to move any data from the source to the target that does not already exist in the target, based on this constraint.
• Updates site.app_db_name to the database name of the target database
• Updates site_link_info.linked_server_name to the server name of the target database for all rows where site_link_info.to_site = site being moved

Data within some tables, for example AuditLog, BGTaskHistory_mst, and tables whose names start with "import" is not copied with this process.

If the source site is in a database that contains other sites, the data is filtered so that only the specified site’s data is copied.