Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system. A migration system then accesses the migration package and begins migrating the data to its destination, from the cloud-based storage system.

Abstract: Various systems and methods for domain authentication are described herein. In an example, the method may include detecting a domain from a request of a tenant for access to a farm. The method may also include identifying a presence of a site ID from a database of the farm based on the domain. The method may also include sending an authentication request to a default site or a custom site, the authentication request managed through a site manager based on the identified presence of the site ID in the database of the farm. The method may also include routing traffic from the tenant to the farm in response to satisfaction of the authentication request.

Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system. A migration system then accesses the migration package and begins migrating the data to its destination, from the cloud-based storage system.

Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system. A migration system then accesses the migration package and begins migrating the data to its destination, from the cloud-based storage system.

Abstract: Aspects of the present disclosure provide systems and methods for directly transferring tenant data hosted on a source domain to a target domain, wherein the source and target domains are associated with different server farms. Additionally, where the source domain is managed by a source management layer and the target domain is managed by target management layer, which source and target management layers are not in a trust relationship. Aspects describe establishing a secure, direct communication bus between the source and target management layers in order to accomplish a plurality of steps involved in transferring the tenant, wherein tenant data transferred thereon is encrypted. In example aspects, the direct communication bus terminates upon completion of the tenant data transfer.

Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system. A migration system then accesses the migration package and begins migrating the data to its destination, from the cloud-based storage system.

Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system. A migration system then accesses the migration package and begins migrating the data to its destination, from the cloud-based storage system.

Abstract: Aspects of the present disclosure provide systems and methods for directly transferring tenant data hosted on a source domain to a target domain, wherein the source and target domains are associated with different server farms. Additionally, where the source domain is managed by a source management layer and the target domain is managed by target management layer, which source and target management layers are not in a trust relationship. Aspects describe establishing a secure, direct communication bus between the source and target management layers in order to accomplish a plurality of steps involved in transferring the tenant, wherein tenant data transferred thereon is encrypted. In example aspects, the direct communication bus terminates upon completion of the tenant data transfer.

Abstract: Various systems and methods for domain authentication are described herein. In an example, the method may include detecting a domain from a request of a tenant for access to a farm. The method may also include identifying a presence of a site ID from a database of the farm based on the domain. The method may also include sending an authentication request to a default site or a custom site, the authentication request managed through a site manager based on the identified presence of the site ID in the database of the farm. The method may also include routing traffic from the tenant to the farm in response to satisfaction of the authentication request.

Abstract: A cloud-based migration system exposes a source-independent application programming interface for receiving data to be migrated. The data is uploaded and stored as a single entity in a cloud-based storage system.

Abstract: Various technologies and techniques are disclosed for extracting data from databases of content management applications. Input is received from a user to connect to a database of a content management application. A connection is established to the database. When the database is not part of a current live instance of the content management application, an emulation is performed so that the database is treated like it is actually attached to the current live instance of the content management application. The user is able to browse the database. Unattached databases of a content management application can be managed using one or more commands, such as using an object model or command line. Orphaned databases can be detected and deleted from the content management application.

Abstract: Technologies are described herein for managing database snapshots. One user interface is provided for managing the automated creation and deletion of database snapshots. Parameters are received through the user interface that define how the database snapshots should be created and deleted. Once the parameters are defined, a timer job is executed that causes a DBMS to create and delete the database snapshots according to the specified parameters. A user interface is also provided for manually managing the creation, deletion, and restoration of database snapshots. A request may be received through this user interface to recover data from a database snapshot. In response to such a request, another user interface is provided for specifying the data that should be recovered. Once the data to be recovered has been specified, the desired data is recovered from the database snapshot.

Abstract: Technologies are described herein for managing database snapshots. One user interface is provided for managing the automated creation and deletion of database snapshots. Parameters are received through the user interface that define how the database snapshots should be created and deleted. Once the parameters are defined, a timer job is executed that causes a DBMS to create and delete the database snapshots according to the specified parameters. A user interface is also provided for manually managing the creation, deletion, and restoration of database snapshots. A request may be received through this user interface to recover data from a database snapshot. In response to such a request, another user interface is provided for specifying the data that should be recovered. Once the data to be recovered has been specified, the desired data is recovered from the database snapshot.

Abstract: Various technologies and techniques are disclosed for extracting data from databases of content management applications. Input is received from a user to connect to a database of a content management application. A connection is established to the database. When the database is not part of a current live instance of the content management application, an emulation is performed so that the database is treated like it is actually attached to the current live instance of the content management application. The user is able to browse the database. Unattached databases of a content management application can be managed using one or more commands, such as using an object model or command line. Orphaned databases can be detected and deleted from the content management application.