> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell/powershell-commands/convert-from-rdmwebsitelegacyentry.md).

# Convert-From-RDMWebsiteLegacyEntry

### Synopsis <a href="#synopsis" id="synopsis"></a>

Convert a legacy Website entry to the modern Website entry type.

### Syntax <a href="#syntax" id="syntax"></a>

`ConvertFrom-RDMWebsiteLegacyEntry -InputObject <PSConnection> [-ForcePromptAnswer <Cancel | No | Yes>] [<CommonParameters>]`

### Description <a href="#description" id="description"></a>

Convert a legacy Website entry to the modern Website entry type. The converted entry is returned but not saved — pipe the result to Set-RDMEntry to persist the change.

### Parameters <a href="#parameters" id="parameters"></a>

#### -ForcePromptAnswer <a href="#forcepromptanswer" id="forcepromptanswer"></a>

Switch to use with caution. It will automatically answer prompt asking yes/no, yes/no/cancel, or ok/cancel questions. In case of multiple prompts, multiple values can be passed to this parameter. Here are the accepted values:

* Yes: Accept the prompt. Cover the OK and Automatic value.
* No: Refuse the yes/no/cancel prompt. Cancel is the fallback option if there is not an option No.
* Cancel: Cancel the yes/no/cancel prompt. No is the fallback option if there is not an option Cancel.

```
Required? false
Position? named
Default value
Accept pipeline input? false
Aliases Accept wildcard characters? false
```

#### -InputObject <a href="#inputobject" id="inputobject"></a>

PSConnection object containing the legacy Website entry to convert.

```
Required? true
Position? 0
Default value
Accept pipeline input? true (ByValue)
Aliases
Accept wildcard characters? false
```

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Inputs

**RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnection** Legacy Website entry to convert, obtained from Get-RDMEntry.

### Outputs

**RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnection** Converted Website entry.

### Notes

For more information, type "Get-Help ConvertFrom-RDMWebsiteLegacyEntry -detailed". For technical information, type "Get-Help ConvertFrom-RDMWebsiteLegacyEntry -full".

### Example

```powershell
Get-RDMEntry -Type DataEntry |
        Where-Object { $_.DataEntry.ConnectionTypeInfos | Where-Object { $_.DataEntryConnectionType -eq 'Web' } } |
        ConvertFrom-RDMWebsiteLegacyEntry |
        Set-RDMEntry
```

Convert all legacy Website entries in the current vault to the modern Website type and save them. The Where-Object filter is needed because -Type DataEntry retrieves all entries under the 'Information' category — the filter narrows to legacy Website entries specifically, skipping other sub-types (Credential, Secure Note, etc.). The converted entry keeps the original ID, so Set-RDMEntry overwrites the legacy entry in place.

### Related links

* [Get-RDMEntry](https://docs.devolutions.net/powershell/powershell-commands/get-rdmentry/)
* [Set-RDMEntry](https://docs.devolutions.net/powershell/powershell-commands/set-rdmentry/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/powershell/powershell-commands/convert-from-rdmwebsitelegacyentry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.