> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/making-the-transition/how-to-import-your-spectora-templates-into-scribeware.md).

# How to import your Spectora templates into ScribeWare

Importing your Spectora templates into ScribeWare just takes a few steps, and will help give you a head start on your transition into a best solution for your business!

To import your Spectora templates, perform the following steps:

1. Export your template to a spreadsheet by following the directions on Spectora's support site, here: <https://support.spectora.com/en/articles/2769896-export-template-to-spreadsheet>
2. Create an account in ScribeWare, if you haven't already
3. Email the exported spreadsheet to our team at <support@getscribeware.com>. We'll get the template imported for you!
4. Bonus points for sending us a sample report as well. This can help us make the import more accurate.

Of course, the resulting template won't take advantage of the many great features that ScribeWare has to offer, such as [Gunnyscaks](https://docs.scribeware.com/advanced-workflows/gunnysacks-and-magic-captions.md) and [linked comment](https://docs.scribeware.com/customizations/template-customization/building-links-for-instant-comments.md)s, but your existing language and structure will be carried over to give a familiar place to start with!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/making-the-transition/how-to-import-your-spectora-templates-into-scribeware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
