page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
Mover uses OAuth to connect to this service. Save the connection, then select *Connect Your Account* and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.
## Multiple Box Accounts
You can add multiple Box Connections, each associated with a different Box account.
Your browser may automatically select an existing Box session when you add another account. Sign out of Box in the browser before adding the new connection if you need to authenticate as a different user.
## page.vars.VENDOR\_NAME is Not Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
## Migration Limits and Performance
Box applies API rate limits and accepts data more slowly than object-storage services such as Amazon S3. Throttling can slow a migration both from and to Box because Mover uses the Box API to list, inspect, download, and upload items. Mover automatically reduces parallel work and retries recognized rate-limit responses with increasing delays. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits) for planning recommendations.
Folder size also affects Box listing and API performance. Folders with 250 to 500 items provide the most stable migration behavior. Performance can become noticeably slower near 1,000 items, with further degradation likely beyond that, so divide larger folders before migrating when possible.
Mover cannot upload a file larger than 15 GB to a Box destination. A dry run records oversized files before the live transfer.
## Troubleshooting
### Insufficient Permissions
Make sure the permissions of the Box user account are correct. Mover can only perform actions that are allowed for the Box user, so the connected account needs "Editor" permissions or higher.
Some actions are not allowed for Box "Viewer" permissions unless the user performs those actions on the Box platform itself. A "Viewer" action that succeeds on the Box platform will not succeed for the same user when they access Box through Mover.
### Disabled Connection
Because Box uses the OAuth authorization protocol, authentication can fail later even after your Connection and Migration have run successfully for some time.
Once you've resolved the problem that caused the authentication error, re-enable your Connection by saving its configuration. Saving the record causes Mover to re-enable the connection so that any associated Migrations will begin working again, even when no fields have changed.
# Dropbox
## Connections
Create a new connection and select page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
Mover uses OAuth to connect to this service. Save the connection, then select *Connect Your Account* and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.
## page.vars.VENDOR\_NAME is Not Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
## Rate Limiting
Dropbox throttles requests from external integrations. A migration can be rate-limited when Dropbox is either the source or destination because Mover uses the Dropbox API to list, inspect, download, and upload items. Upload-heavy migrations are especially likely to be constrained by the rate Dropbox accepts.
Mover automatically reduces parallel work and retries recognized rate-limit responses with increasing delays. If Dropbox continues rejecting an item after those retries, the run records a failure that can be retried by running the migration again. Mover does not expose a Dropbox concurrency setting, so use smaller, non-overlapping batches and run them one at a time. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits).
Dropbox also restricts some filenames and file types. Run a dry run and rename or exclude unsupported items before the live migration.
# Google Drive
## Connections
Create a new connection and select page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
Mover uses OAuth to connect to this service. Save the connection, then select *Connect Your Account* and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.
Mover can access the connected account's personal drive, Shared Drives, and folders that other Google Drive users have shared with the account.
## Migration Destination
When Google Drive is the destination, select `My Drive`, a writable Shared Drive, or a folder within a drive, such as `My Drive/Incoming`. The top level of the connection lists drives and shared content; it is a browsing level and cannot receive files.
The migration's *Destination Path* is required for Google Drive. Leaving it blank selects the read-only connection root, which Mover rejects when creating or editing a migration. Selecting a path does not establish write permission: the connected Google account must be able to upload files to the selected drive or folder. The connection root can still be used as a migration source.
## Google Workspace Files
Google Docs, Sheets, and Slides are not stored as ordinary downloadable files. Mover exports them to Microsoft Office formats during migration: Docs become `.docx`, Sheets become `.xlsx`, and Slides become `.pptx`.
When migrating between two Google Drive accounts, Mover uses an internal `.google-apps` marker while processing the converted file and removes that marker before uploading it to the destination. A source Google Sheet named `Budget` therefore arrives as `Budget.xlsx`. It is not converted back into a native Google Sheet.
## Duplicate and Unsupported Names
Google Drive permits several files in one folder to have the same name. A filesystem migration cannot represent those files as distinct paths, so Mover skips case-insensitive duplicate names and records the conflict in the run log. Rename the files in Google Drive before rerunning the migration.
Google Drive also permits `/` and `\` in filenames, but Mover treats those characters as path separators or invalid path characters. Rename files containing either character before migration.
## Rate Limiting and Listing Speed
Google Drive can rate-limit migrations in either direction. It also does not use filenames as unique identifiers, so Mover must list an entire folder to resolve a file by name. Large folder trees can therefore take a long time to scan even when only a small amount of data needs to move.
Mover automatically reduces parallel work and retries recognized rate-limit responses with increasing delays. Mover does not expose a Google Drive concurrency setting. Divide large migrations into non-overlapping source paths or include-pattern batches and run them one at a time. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits).
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# OneDrive
## Connections
Adding a OneDrive connection has two steps: save the connection, then sign in to OneDrive and authorize Mover to access your files.
Create a new connection and select page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
Choose the type of account, either Business or Personal OneDrive account, and then save the entry to continue.
Mover uses OAuth to connect to this service. Save the connection, then select *Connect Your Account* and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.
## page.vars.VENDOR\_NAME is Not Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# SharePoint
## Connections
Adding a page.vars.VENDOR\_NAME connection is a two-step process. First, you save a new connection. After the connection is saved, you log into page.vars.VENDOR\_NAME to grant Mover access to your files.
Create a new connection and select page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
Mover uses OAuth to connect to this service. Save the connection, then select *Connect Your Account* and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.
## Migration Destination
When SharePoint is the destination, select a document library or a folder inside one. A destination such as `companyname.sharepoint.com/sites/MySite/Shared Documents` selects the site's default document library; `companyname.sharepoint.com/sites/MySite/Shared Documents/Incoming` selects a folder within it. The default library appears as `Shared Documents` in the path even when SharePoint displays it as *Documents*.
The connection root and site levels let you browse to libraries; they cannot receive files. The migration's *Destination Path* is required for SharePoint, and Mover rejects an empty destination path when creating or editing a migration. A site path by itself, such as `companyname.sharepoint.com/sites/MySite`, is also not a writable file destination. A nonempty path still needs to identify a library or folder where the connected account can upload files; accepting the path does not confirm write permission.
The connection root can be used as a migration source. A [OneDrive](/connections/cloud-content-platforms/onedrive) connection points directly to a drive and supports a root destination.
## page.vars.VENDOR\_NAME is Not Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
## SharePoint Changes to Uploaded Files
SharePoint can add metadata to an uploaded Office file, changing its size after Mover delivers it. Mover detects the size change and copies the SharePoint-modified version back to the migration source so later runs do not transfer the file repeatedly. The run log records this as a `sync_remote_resync` operation.
This is the one situation in which a migration configured to keep source files can still write to the source. When SharePoint is the destination, make sure the source connection is writable. Otherwise, the resync fails and later runs can repeatedly transfer the same file.
Files that are checked out, open in Microsoft Office Online, or otherwise locked in SharePoint cannot be migrated until the lock is released.
## Rate Limiting
[Microsoft applies throttling limits to SharePoint Online](https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online), and the applicable limit can depend on the Microsoft 365 license plan. A migration with many files can reach the limit whether SharePoint is the source or destination.
Mover automatically reduces parallel work and retries recognized throttling responses with increasing delays. If SharePoint continues rejecting an item after those retries, the run records a failure that can be retried by running the migration again. Mover does not expose a SharePoint concurrency setting, so use smaller, non-overlapping batches and run them one at a time. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits).
# Object Storage
Object storage connections are designed for bucket or container services. They generally handle large migrations more efficiently than collaboration platforms because they expose direct storage APIs without the same document-collaboration layer.
Mover provides dedicated connections for:
* [Amazon S3](/connections/object-storage/amazon-s3)
* [Azure Blob Storage](/connections/object-storage/azure-blob-storage), including containers that use Azure Data Lake Storage Gen2 hierarchical namespaces
* [Google Cloud Storage](/connections/object-storage/google-cloud-storage)
Use [S3-Compatible Storage](/connections/object-storage/s3-compatible-storage) for another service that implements the S3 protocol. Mover also provides named S3-compatible connection forms for [Akamai Linode](/connections/object-storage/s3-compatible-storage/akamai-linode), [Backblaze B2](/connections/object-storage/s3-compatible-storage/backblaze-b2), [Cloudflare R2](/connections/object-storage/s3-compatible-storage/cloudflare-r2), [Filebase](/connections/object-storage/s3-compatible-storage/filebase), and [Wasabi](/connections/object-storage/s3-compatible-storage/wasabi).
Object storage connections require a bucket or container and provider credentials. Prefer credentials scoped to the migration's required paths and actions. A source-only connection can use read-only access; a destination must allow object creation, and source deletion requires delete permission.
Amazon S3, Azure Blob Storage, and Google Cloud Storage sources support additional detection when a source object changes during a run. See [File Matching and Data Integrity](/migration-behavior/file-matching-and-data-integrity).
# Amazon S3
AWS S3 connections let you move files to or from your S3 buckets.
## Connections
Create a new connection and choose AWS S3 as its type.
Provide a *Connection Label* so you can identify the connection in a list. This matters most when you have more than one connection of the same type, like two S3 buckets used as separate endpoints in the same workflow.
### Bucket Details
Enter the name of the bucket to use for the connection.
Choose the AWS Region where your bucket resides.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3. We recommend using AWS IAM to create an IAM user just for Mover.
After generating the IAM User, copy its Access Key and Secret Key to your Connection.
### Advanced Settings
If your S3 user policy does not have access to the entire bucket, or is restricted to specific subfolders only, then verification of access to the bucket may fail when testing credentials.
Use the advanced setting for *Can these credentials access the root of this remote or are they restricted to a subfolder?* to specify a subfolder that can be used to verify access when testing your credentials.
## Required Permissions for IAM User
### Minimal Permissions for Full Access
If you are copying data to this connection, apply a policy to the IAM user to grant it full permissions to the bucket being used. These permissions represent the minimum required for Mover to function correctly with your S3 bucket.
To use the below example, replace `page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Azure Blob Storage
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Account Details
*Account* - The name of your Azure Storage Account, as shown in your *Microsoft Azure web portal > Home > Storage Accounts* page.
*Container* - The name of your Azure Container, as shown in your *Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Data Storage > Containers* page.
Check the box for *Use Hierarchical Namespace (Azure Data Lake Storage Gen2)* only if you have enabled the [hierarchical namespace](https://learn.microsoft.com/en-us/azure/storage/blobs/create-data-lake-storage-account#enable-the-hierarchical-namespace) option for your Azure Container.
### Credentials
Mover can authenticate to page.vars.VENDOR\_NAME using either an Access Key or SAS Token. If you're using *Access Key*, copy the value from your *Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Access Keys.* For the SAS Token, copy the value from your *Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Shared Access Signature* page.
### Advanced Settings
If your credentials do not have access to the entire container, or are restricted to specific subfolders only, then Mover may not be able to verify the connection works.
When you do not have access to the entire container, use the advanced setting for *Can these credentials access the root of this remote or are they restricted to a subfolder?* to specify a subfolder that can be used instead.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Google Cloud Storage
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Enter the name of the bucket to use for the connection.
The Project ID is the unique identifier for your Google Cloud project. Mover uses it to identify which project's resources to interact with.
### Credentials
Provide the JSON key for a Google Cloud service account that can access the bucket. Create and download the key from Google Cloud; see [Google's service account key documentation](https://cloud.google.com/iam/docs/keys-create-delete).
### Advanced Settings
If your credentials do not have access to the entire bucket, or are restricted to specific subfolders only, then Mover may not be able to verify connection to the bucket.
When you do not have access to the entire bucket, use the advanced setting for *Can these credentials access the root of this remote or are they restricted to a subfolder?* to specify a subfolder that can be used instead.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# S3-Compatible Storage
Mover's S3-compatible connection type lets you connect to private cloud services that speak the S3 protocol, including IBM Cloud, Oracle Cloud, Minio, and DigitalOcean Spaces.
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Enter the name of the bucket to use for the connection.
Enter the API endpoint for the bucket.
Enter the region where the bucket resides if the provider requires it.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3. Check your storage provider's documentation for how to create the access key and secret key.
## Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
Check the documentation on your storage provider to determine whether you need to account for case sensitivity differences.
# Akamai Linode
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Enter the name of the bucket to use for the connection.
Choose the Region where your bucket resides.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.
*Access Key* — the Linode Object Storage *Access Key*, as shown in your *Linode web portal > Object Storage > Access Keys* page.
*Secret Key* — the *Secret Key* that corresponds to the above Access Key, which was shown to you when you first created the *Access Key*.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Backblaze B2
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially useful when you have more than one connection of the same type.
### Bucket Details
Enter the name of the bucket to use for the connection.
Enter the endpoint for your Backblaze bucket. It will have a format like `https://s3.page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Cloudflare R2
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Enter the Cloudflare R2 bucket name shown under *R2 > Overview* in the Cloudflare dashboard.
For *Cloudflare Endpoint*, enter the URL listed as *S3 API* in the Cloudflare dashboard. Do not append the bucket name.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.
*Cloudflare Access Key* - The Cloudflare R2 Access Key ID, as shown in your *Cloudflare web portal > My Profile > API Tokens* page, or in your *Cloudflare web portal > R2 > Overview > Manage R2 API Tokens* page.
*Cloudflare Secret Key* - The Secret Access Key that corresponds to the above Access Key ID, as shown in your *Cloudflare web portal > My Profile > API Tokens* page, or in your Cloudflare web portal > R2 > Overview > Manage R2 API Tokens page.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Filebase
Mover connects to Filebase buckets through Filebase's S3-compatible interface. Filebase stores data using IPFS, the InterPlanetary File System.
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Fill the *Filebase Bucket Name* with the name of your bucket from your *Filebase web portal > Buckets* page.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.
Use the [Access Keys dashboard](https://docs.filebase.com/api-documentation/s3-compatible-api#access-keys) in your Filebase account to create and manage your keypair.
Enter the key in *Filebase Access Key* and the secret in *Filebase Secret Key*.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Wasabi
## Connections
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Bucket Details
Fill the *Wasabi Bucket Name* with the name of your bucket as shown in the Wasabi Management Console.
Enter the region code for your bucket. For example, if your region URL is `us-east-1.s3.wasabisys.com`, then your region code is `us-east-1`.
### Credentials
Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.
In the Wasabi Management Console, create an access key and assign it to a user who has access to your bucket. Store the Access Key and the Secret Key in the credentials section in your new connection in Mover.
## page.vars.VENDOR\_NAME is Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# File Servers and Protocols
Mover can connect to file servers directly over a supported protocol or through the Files.com Agent. The right method depends primarily on whether Mover can reach the server over the public internet.
Use a direct [FTP/FTPS](/connections/file-servers-and-protocols/ftp-ftps), [SFTP](/connections/file-servers-and-protocols/sftp), or [WebDAV](/connections/file-servers-and-protocols/webdav) connection when the server has a publicly resolvable address and its firewall permits the required traffic. Prefer an encrypted protocol and keep server identity verification enabled. FTP and SFTP connections expose a *Max Connections* setting for servers that need a lower connection count.
Use [Azure Files](/connections/file-servers-and-protocols/azure-files) for a Microsoft Azure file share.
Use the [Files.com Agent](/connections/file-servers-and-protocols/files-com-agent) for local disks, network-attached storage, or other storage on a private network. The Agent makes an outbound connection, so it does not require an inbound firewall rule. Install it on a host that can reach the migration data and choose a root folder that limits what the connection can access.
The server or host filesystem determines case sensitivity and can impose additional filename, path-length, locking, and permission behavior. Review [File and Folder Compatibility](/migration-behavior/file-and-folder-compatibility) and run a dry run before the live transfer.
# Files.com Agent
The Files.com Agent connects Mover to servers that aren't directly accessible over the public internet, including on-premises file servers. With the Files.com Agent, you can migrate files to and from a host's local disks and drives, and from network-attached storage the host can reach over CIFS, SMB, or NFS.
## Connections
Adding an Agent connection has three parts: save the connection in Mover, download its configuration file, and install the Agent as a service on the host system.
### New Agent Connection
Create a new connection and choose page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This matters most when you have more than one connection of the same type, since the label is what tells them apart.
#### Agent Configuration
Choose the *Agent Permissions* that Mover should have on the host system. Select *Read and Write* when the Agent will be a migration destination. Select *Read Only* when it will only be a source.
Set *Agent Root Folder* to an existing path on the host system. The connection can access only files and folders within this root.
Save the Connection to continue.
### Configuration File
Edit the Agent connection in Mover and select *Download Configuration File*. The file contains the connection credentials and Agent settings, including logging and automatic updates.
### Agent Installation
Download the Agent executable from the [official download page](https://filescorp.hosted-by-files.com/builds/files-agent-server/latest). Choose the build for the host operating system and architecture, save it with the configuration file, and install the Agent as a system service on [Windows](/connections/file-servers-and-protocols/files-com-agent/windows-installation), [macOS](/connections/file-servers-and-protocols/files-com-agent/macos-installation), or [Linux](/connections/file-servers-and-protocols/files-com-agent/linux-installation).
### Connection Status
After you install and start the Agent service, check the connection in Mover. A *Connected* status means the connection is ready to use.
If the status is *Waiting for connection*, verify that the Agent service is running on the host.
## Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
Check the documentation on your host system to determine if you need to account for case sensitivity differences.
# Windows Installation
Install the Files.com Agent as a Windows service so it starts at boot, runs without a user session, and restarts after a failure.
## Root Path
Verify that the `root` setting in the [configuration file](/connections/file-servers-and-protocols/files-com-agent/agent-configuration-file) uses either a local drive path (for example, `C:\path\to\folder`) or a UNC path to an accessible network drive (for example, `\\servername\c$\path\to\folder`).
Microsoft advises using [UNC paths instead of mapped network drives for system services](https://learn.microsoft.com/en-us/windows/win32/services/services-and-redirected-drives) because mapped drives can cause security and reliability problems. Mapped drives are shared across accounts, so other services may gain unintended access.
## Service Account Permissions
The Windows service account running the Agent needs the right permissions to access the folder defined in the configuration file's `root` setting.
For most environments, a named Active Directory account is the best practice. Configure the service to log on as this account and verify that it exists on both the Agent host system and any remote system the UNC path references. This account must also have the "[Log on as a service](https://learn.microsoft.com/en-us/system-center/scsm/enable-service-log-on-sm)" privilege. The Agent can only access the `root` items that the selected user account has permissions to access. If you choose a local system user account instead, verify the same account exists and has appropriate access on both systems.
## MSI-Based Service Installation
For a 64-bit x86 Windows system, download the MSI installer from the [Agent download page](https://filescorp.hosted-by-files.com/builds/files-agent-server/latest).
Place the MSI file in the same folder as the Agent configuration file before installation. Once you've updated the [configuration file](/connections/file-servers-and-protocols/files-com-agent/agent-configuration-file), run the MSI to install the Agent as a service.
After installation, you'll find the configuration file at `C:\Program Files\Files.com-Agent\files_agent_config.toml`.
## Command-Line Service Installation
You can also install the Agent as a Windows service by using the command:
```powershell
files-agent.exe service install --config C:\path\to\files_agent_config.toml
```
When you install the Agent this way, the executable and configuration file stay in their current locations. After installation, start the service from the command line by running:
```powershell
files-agent.exe service start
```
If you need to update the configuration file, stop the service first, make your changes, and then restart the service.
To stop it via the command line, use:
```powershell
files-agent.exe service stop
```
To remove the Agent service from the system, use the command:
```powershell
files-agent.exe service uninstall
```
# macOS Installation
On macOS, you install the Files.com Agent as a service so it starts automatically when the system powers on or reboots, and so it restarts itself if the agent program needs to recover from a problem. Running the Agent as a service is what makes the connection reliable across restarts and crashes.
## Root Path
Before you install the Agent as a service, set the `root` setting in the configuration file to either a local drive path (`/path/to/folder`) or a path to an accessible mounted network drive (`/mnt/path/to/folder`).
## Agent Download
Download the agent executable for your system from the [official download location](https://filescorp.hosted-by-files.com/builds/files-agent-server/latest). Choose the version with "macos" in the name that matches your architecture and save it to the same location as your configuration file on the host system.
## Service Installation
To install the Agent as a `launchd` service on macOS, run:
```bash
files-agent service install --config /path/to/files_agent_config.toml
```
This method keeps the executable and configuration file in their original locations.
Start the service with:
```bash
files-agent service start
```
If you update the configuration file, stop the service, make your changes, and restart it.
Stop the service with:
```bash
files-agent service stop
```
Remove the service with:
```bash
files-agent service uninstall
```
# Linux Installation
Running the Files.com Agent as a system service starts it automatically at boot and keeps it running independently of user logins.
## Root Path
Before you install the Agent as a service, make sure that the `root` setting in the configuration file uses either a local drive path (such as `/path/to/folder`) or a path to an accessible mounted network drive (such as `/mnt/path/to/folder`).
## Agent Download
Download the agent executable for your system from the [official download location](https://filescorp.hosted-by-files.com/builds/files-agent-server/latest). Choose the version that matches your architecture and operating system and save it to the same location as your configuration file on the host system.
## Service Installation
To install the Agent as a service on a Linux system, run the following command:
```bash
files-agent service install --user-service=false \
--config /path/to/files_agent_config.toml
```
Start the service with:
```bash
files-agent service start
```
If you modify the configuration file, stop the service, make your updates, and then restart it.
To stop the service, use:
```bash
files-agent service stop
```
When you're ready to remove the Agent service, run:
```bash
files-agent service uninstall --user-service=false
```
## Optional systemd Installation
If the Linux system uses `systemd`, you can install the Agent by creating a service unit. For another init system, follow that system's service documentation.
Create a file at `/lib/systemd/system/files-agent.service` with the following content:
```ini
[Unit]
Description=Files.com Agent v2
ConditionFileIsExecutable=/usr/bin/files-agent
[Service]
StartLimitInterval=5
StartLimitBurst=10
ExecStart=/usr/bin/files-agent "start" "--config" "/path/to/files_agent_config.toml" "--log_file" "/path/to/files-agent.log"
Restart=always
RestartSec=60
[Install]
WantedBy=multi-user.target
```
Replace the `ExecStart` paths (config file and log file) with the correct locations for your configuration and log files.
After creating the service file, install and enable it using:
```bash
sudo systemctl enable files-agent
```
Start the service with:
```bash
sudo systemctl start files-agent
```
To change the configuration, stop the service, edit the configuration file, then restart the service.
Stop the service with:
```bash
sudo systemctl stop files-agent
```
Remove the service with:
```bash
sudo systemctl disable files-agent
```
# Agent Configuration File
Mover generates a Files.com Agent configuration file when you create the Agent connection. Download it from the connection's setup page.
The file uses [TOML](https://toml.io/) syntax and can be reviewed and customized by the system administrator before the Agent starts.
Prior to use, the system administrator can review and update the following fields of the TOML file:
root | The top-level directory the Agent can access. Enclose the path in single quotes, such as '/path/to/agent/folder', 'C:\windows\folder', '/mnt/otherserverfolder', or '\\networkservername\c$\folder'. The user or service account running the Agent must have access to the path. Mount network locations on the host before starting the Agent. |
permission_set | The Agent's access level. Valid values are read_write, read_only, and write_only. |
follow_links | Whether the Agent can follow links to folders outside root. Valid values are true and false. The default is false. |
auto_update_policy | How the Agent installs updates. Valid values are always, critical_only, manual_trigger, and never. The default is always. |
override_max_concurrent_jobs | The maximum number of jobs the Agent processes at once. The default is 500. Increase this value only after testing the host's available memory and I/O capacity. |
show_hidden_files | Whether the Agent can access hidden files and folders on Windows. Valid values are true and false. The default is false. |
id | The unique ID for this Agent connection. Do not edit it. |
private_key | The private key that authenticates this Agent. Do not edit or disclose it. |
subdomain | The Files.com custom subdomain associated with the Agent. |
prefer_protocol | The preferred connection protocol. The Agent uses UDP by default and falls back to TCP when UDP is unavailable. Set this to tcp to use only TCP. |
dns | The DNS lookup method. Valid values are auto, doh, and system. The default auto method tries public DNS before falling back to system DNS. doh uses DNS over HTTPS through https://cloudflare-dns.com; system uses the host's DNS settings. |
proxy_all_outbound | Whether all Agent connections are proxied through Files.com. Enable this when network policy prevents the Agent from connecting directly to external services. |
endpoint_override | The custom domain the Agent uses when connecting to Files.com. |
log_file | The log file name and location. When blank, the Agent uses its default log location. |
log_level | The minimum severity written to the Agent log. Valid values are debug, info, warn, error, and fatal. The default is info; debug produces the largest and most detailed logs. |
log_rotate_num | The number of rotated log files to retain. The default is 5. |
log_rotate_size | The log file size in MB that triggers rotation. The default is 20. A value of 0 uses the default. |
graceful_shutdown_timeout | The number of seconds allowed for in-progress tasks to finish during shutdown. The default is 15. A value of 0 uses the default. |
transfer_rate_limit | The Agent upload and download bandwidth cap. The default is unlimited. Set a limit when the Agent must avoid saturating a constrained network. This setting does not control rate limits imposed by a cloud provider. |
page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Account Details
*Azure Files Account* - The name of your Azure Storage Account, as shown in your *Microsoft Azure web portal > Home > Storage Accounts* page.
*Azure Share Name* - The name of your Azure file share, as shown in your *Microsoft Azure web portal > Home > Storage Accounts > selected storage account > File shares* page.
### Credentials
Mover can authenticate to page.vars.VENDOR\_NAME with an access key or SAS token. Copy the access key from *Home > Storage Accounts > selected storage account > Access Keys* in the Azure portal. Copy the SAS token from *Home > Storage Accounts > selected storage account > Shared Access Signature*.
### Advanced Settings
To connect to Azure Files storage in US Government Azure, set the advanced setting for the *Azure DNS Suffix* to `core.usgovcloudapi.net`.
## page.vars.VENDOR\_NAME is Not Case Sensitive
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# FTP/FTPS
Mover can connect to servers that accept FTP or FTPS connections.
## Connections
Add a new connection and select FTP as the connection type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.
### Server
Enter a publicly resolvable fully qualified domain name or IP address that Mover can reach.
Use the default port value of 21 for FTP unless you know the FTP server requires an alternate port. The other commonly used port, 990, typically means that the server requires SSL using the Implicit method. When using port 990, you also need to select *Require SSL (implicit)* under the SSL selection.
### Credentials
Enter the username that will be used for the FTP connection, and provide the password. FTP connections do not support the use of SSH/SFTP keys for authentication.
### SSL
You can customize how Mover will use SSL on this connection.
Choose *Require SSL (explicit)* or *Require SSL (implicit)* when encryption is required. *Use if available* can fall back to plain FTP when the server does not offer TLS.
Choose *Never use SSL* only when the server does not support FTPS. Plain FTP sends credentials and file contents without encryption.
### Server Certificate
The TLS certificate helps Mover verify the identity of the FTPS server and detect attempts to impersonate it.
By default, Mover requires the certificate to match the connection hostname and chain to a trusted certificate authority. You can relax this requirement for a self-signed or non-matching certificate, but doing so weakens server identity verification.
### Max Connections
You can configure a maximum number of connections to the FTP server that Mover will open at once. We recommend the default value of 25, which provides a high level of parallelism and improves performance.
Some server administrators will request that you reduce this number to reduce the pressure on their server. Reducing it too low will reduce performance because requests may have to wait for a free connection before they are able to complete.
Mover will use best efforts to honor the maximum number specified here, though it may still burst above this number on certain occasions, such as when moving the connection to another one of our gateway servers internally. As a cloud-based service, we often reconfigure our network in real time to provide optimized performance. If we ever temporarily exceed the configured maximum, expect the connection count will return to the specified number promptly.
## Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
Check the documentation on your storage providers to determine if you might need to account for case sensitivity differences.
## Troubleshooting
Make sure your connection info matches the required settings of your FTP server. The FTP protocol supports distinct methods and a variety of options that determine whether a client application can connect. If your connection is misconfigured, Mover won't be able to access your files.
### FTPS Methods
FTPS is TLS/SSL-secured FTP. It has been implemented in two non-compatible methods.
The current recommended method is [Explicit FTPS](https://en.wikipedia.org/wiki/FTPS#Explicit), which implements TLS on standard FTP ports, starting with TCP port 21.
The older, deprecated method is [Implicit FTPS](https://en.wikipedia.org/wiki/FTPS#Implicit), which implements TLS on TCP port 990.
Confirm which method of FTPS your server uses, and make sure your connection matches the requirements.
### SSL Certificate Validity
By default, Mover expects the FTPS server certificate to match the connection hostname, be valid for the current date, and chain to a trusted certificate authority.
If the certificate does not meet those requirements, configure the FTP connection to allow an untrusted certificate only after verifying the certificate and understanding the security tradeoff.
If you're not sure if the server's certificate is fully valid, there are many online tools available for checking the validity of a site's certificate, such as the [SSL Shopper SSL checker](https://www.sslshopper.com/ssl-checker.html) and the [DigiCert SSL certificate checker](https://www.digicert.com/help/).
### Firewalls
The FTP(S) server may be behind a firewall that only allows connections from specified IP addresses. If a firewall is blocking Mover's IP addresses, the firewall must be updated to allow Mover to connect.
Mover connects to the FTP(S) server using Passive (PASV) Mode. In this mode, the FTP(S) server indicates which ports to use in order to traverse any firewalls.
### Partial Connectivity
The FTP protocol uses different connection ports for Control and for Data. The Control channel is used for authentication and for control messages, such as navigating folders, listing folder contents, and setting transmission options. The Data channel is used for the transmission of file content.
If you can connect, navigate folders, and list folder contents, but not upload or download file content, then it's most likely that a firewall is blocking the PASV Data channels. A common symptom of this is having a zero-byte file created whenever an upload or download is attempted. Contact the operator or administrator of the firewall and ask them to ensure that all PASV ports are open on their firewall.
# SFTP
Mover can connect to publicly reachable SFTP servers. FTP or FTPS may provide higher throughput for some migrations; use [FTP/FTPS](/connections/file-servers-and-protocols/ftp-ftps) when the server supports it and the security settings meet your requirements.
## Connections
Add a new connection and select SFTP as the connection type.
Provide a *Connection Label* so you can identify the connection in a list. This is especially important when you have more than one connection of the same type.
### Server
Enter a publicly resolvable fully qualified domain name or IP address that Mover can reach.
The default port for SFTP is 22. Use an alternate port only if you know the SFTP server requires it.
### Credentials
Enter the *Username* that you use for connecting to your SFTP server.
Mover supports authenticating with a password, a private SSH key, or both.
#### Authenticating with Password Only
Choose this option if you log into your SFTP server with a password and do not need to supply an SSH key.
Enter your password in the *Password* field of the connection. Your password is encrypted and stored securely within the Mover platform.
#### Authenticating with Existing Private Key Only
Choose this option if you connect to the SFTP server with an SSH key that you already have.
Upload the private key that Mover will use to log into the server. Your private key is encrypted and stored securely within the Mover platform.
#### Authenticating with New Private Key Only
Choose this option if you will connect to the SFTP server with an SSH key that does not yet exist.
Mover generates a 4096-bit RSA key pair and stores the private key encrypted within the Mover platform.
The public portion of the new key is presented to you, with options to copy it to your clipboard and to download it. The public key must be installed on the SFTP server before you can connect. Send the public key to the server's administrator.
#### Authenticating with Both Password and an Existing Private Key
Choose this option if you connect to the SFTP server with both a password and an SSH key, and you already have the key.
Enter your password in the *Password* field of the connection.
Upload the private key that Mover will use to log into the server.
Your password and private key are encrypted and stored securely within the Mover platform.
#### Authenticating with Both Password and a New Private Key
Choose this option if you connect to the SFTP server with both a password and an SSH key, and the key does not yet exist.
Enter your password in the *Password* field of the connection.
Mover generates a 4096-bit RSA key pair.
Your password and private key are encrypted and stored securely within the Mover platform.
The public portion of the new key is presented to you, with options to copy it to your clipboard and to download it. The public key must be installed on the SFTP server before you can connect. Send the public key to the server's administrator.
### Host Key Verification
Host Key Verification is set to *Require server host key to match* by default. If the server's host key changes, Mover disables the SFTP connection until you verify and update the stored host key. This protects against man-in-the-middle attacks in which another system impersonates the server.
You can change this to *Allow non-matching server host keys*, which may be required in rare cases. This behavior is insecure and not recommended.
### Server Host Key
You can configure a *Server Host Key* for the SFTP server. If you do not provide one at setup, Mover automatically detects the server's host key the first time it connects and stores it for you.
The Server Host Key is not used for user authentication. It is a cryptographic identifier of the SFTP server that confirms each connection reaches the same server.
### Max Connections
You can configure a maximum number of connections to the SFTP server that Mover opens at once. We recommend the default value of 25, which provides a high level of parallelism and improves performance.
Some server administrators will request that you reduce this number to reduce the pressure on their server. Reducing it too low reduces performance, because requests may have to wait for a free connection before they can complete.
Mover uses best efforts to honor the maximum number specified here, but the connection count may temporarily burst above it when Mover moves the connection to another gateway server internally. As a cloud-based service, Mover reconfigures its network in real time to optimize performance. After any temporary excess, the connection count returns to the specified number promptly.
## Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
Check the documentation on your storage providers to determine if you need to account for case sensitivity differences.
## Troubleshooting
Verify that you are using the correct SFTP settings for your connection. Check that the server hostname, port, and authentication information are correct.
Confirm that the outbound server is an SFTP server. The default SFTP port is 22, though some servers use a customized port. If the connection information you received specifies port 21 or 990, the server is an FTP/FTPS server, not SFTP.
# WebDAV
WebDAV extends HTTP with operations for working with files on a remote server. Mover can use a publicly reachable WebDAV server as a migration source or destination.
## Connections
Create a new connection and select page.vars.VENDOR\_NAME as its type.
Provide a *Connection Label* so you can identify the connection in a list.
### Server
Add the *Hostname* for your WebDAV server. The *Hostname* is a fully qualified domain name, not including any protocol prefix or path.
The default *Port* value of `443` is used for HTTPS. Only use an alternate port if the WebDAV server requires it. The other commonly used remote port, 80, typically means the server does not support SSL, in which case select `http://` instead of `https://` under protocol.
Indicate whether the *Protocol* for the connection is `http://` or `https://`. The standard configuration uses `https` for the *Protocol* and `443` for the *Port*.
### Authentication
Mover can authenticate with a username and password or a TLS client certificate.
### Server Certificate
By default, Mover expects the WebDAV server certificate to match the connection hostname, be valid for the current date, and chain to a trusted certificate authority.
If the certificate does not meet those requirements, configure the connection to allow an untrusted certificate only after verifying the certificate and understanding the security tradeoff.
If you're not sure whether the server's certificate is fully valid, online tools are available for checking the validity of a site's certificate. The [SSL Shopper SSL checker](https://www.sslshopper.com/ssl-checker.html) and the [DigiCert SSL certificate checker](https://www.digicert.com/help/) are two options.
## Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
# Billing and Usage Packs
space.vars.MOVER uses prepaid [usage packs](#usage-packs). Purchase the transfer capacity and validity period that fit your migration. The balance decreases as data is transferred and remains available until the pack expires; there is no subscription.
## Usage Packs
Usage packs range from 100 GB to 10 TB. Choose a pack after running a dry run so its capacity reflects the amount of data Mover expects to transfer.
To purchase a new package, open the *Usage Packs* page in your space.vars.MOVER dashboard, choose a package size, and check out.
Each usage pack expires after its stated validity period, calculated from the purchase date. Unused transfer capacity is no longer available after expiration.
## Payment Method
space.vars.MOVER supports payment by credit card or by PayPal.
Add your payment method on the *Billing* page in your account.
Usage packs are charged to the selected payment method at the time of purchase.
## How Data Transfer is Calculated
Only data that is actually transferred during a migration counts toward your usage. Files that are skipped based on your settings do not count as usage. Failed transfer attempts (from connectivity issues, permission errors, and similar problems) do not count as usage.
Running a dry run does not count as usage.
## Usage Pack History
The *Purchase History* page shows the usage packs you have purchased. The table includes:
| Column | Contents |
|---|---|
| Package | The size of the usage pack |
| Purchased | When the pack was purchased |
| Expiration | How many days until the usage pack expires |
| Used | Amount of transfer used |
| Remaining | Amount of transfer remaining |
| Status | Active if the pack is not expired and has remaining usage. Used if there is no transfer remaining for the pack. Expired if the pack's expiration date has passed. |
space.vars.MOVER profile contains your account and contact information. Update it from the *Profile* page.
## Accessing Your Profile
Your *Profile* page is reachable from the main account menu. The profile is organized into three tabs for different types of account information.
Changes you make to your profile take effect immediately.
### Account Tab
On the *Account* tab, you can change your name and your phone number.
### Email Tab
Your email address is used for account login, notifications, and billing receipts. When you enter a new email address, you must also provide your current account password for verification. Requiring the password protects your account from unauthorized changes to login-critical information.
When you change your email address, your account data and migration history remain unchanged.
### Password Tab
On the *Password* tab, you can update the password you use to log into space.vars.MOVER. You must provide your current password as verification when you choose a new password.
Changing your password in your profile does not affect any of your Connections.
space.vars.MOVER enforces password rules to help keep your account secure.
Files.com Support can help configure Mover connections and migrations, review dry-run results, explain usage pack balances, and troubleshoot errors. Support is included at no extra cost.
Email `support@files.com` or call (800) 286-8372.