> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/contract-management/import-contracts.md).

# Import contracts

Use **contract import** when you need to create many contracts at once.

This is useful during migration or large setup work.

### What the import includes

A contract import can include:

* contract data
* work order template data
* recurring schedule data for preventive contracts

### Before you import

Make sure the required reference data already exists.

Examples include contract terms, customers, and other linked records.

Validate the file carefully before import.

### Frequently asked questions

<details>

<summary>Can one import file contain different contract types?</summary>

Yes.

Use the correct type values per row.

</details>

<details>

<summary>What happens when referenced data is missing?</summary>

Those rows can fail validation or import.

</details>

<details>

<summary>Do preventive contracts need schedule data?</summary>

Yes.

Include the fields required for the selected schedule pattern.

</details>

### Related topics

* [**Create and manage contract terms**](/marketplace-packages-and-power-ups/power-ups/contract-management/create-and-manage-contract-terms.md)
* [**Create a contract**](/marketplace-packages-and-power-ups/power-ups/contract-management/create-a-contract.md)
* [**Contract Management**](/marketplace-packages-and-power-ups/power-ups/contract-management.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/contract-management/import-contracts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.