---
title: convert_to_target (v0.46)
description: API reference for qiskit.providers.convert_to_target in qiskit v0.46
source: https://eu-de.quantum.cloud.ibm.com/docs/en/api/qiskit/0.46/qiskit.providers.convert_to_target
---

# qiskit.providers.convert\_to\_target

`qiskit.providers.convert_to_target(configuration, properties=None, defaults=None, custom_name_mapping=None, add_delay=False, filter_faulty=False)`

[GitHub](https://github.com/qiskit/qiskit/tree/stable/0.46/qiskit/providers/backend_compat.py)

Uses configuration, properties and pulse defaults to construct and return Target class.

In order to convert with a `defaults.instruction_schedule_map`, which has a custom calibration for an operation, the operation name must be in `configuration.basis_gates` and `custom_name_mapping` must be supplied for the operation. Otherwise, the operation will be dropped in the resulting `Target` object.

That suggests it is recommended to add custom calibrations **after** creating a target with this function instead of adding them to `defaults` in advance. For example:

```python
target.add_instruction(custom_gate, {(0, 1): InstructionProperties(calibration=custom_sched)})
```