> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/superoffice/import-contacts-from-superoffice-crm.md).
# Import contacts from SuperOffice CRM
When you import contacts from a SuperOffice CRM selection or project, you can include or exclude contacts that lack consent for e-marketing.
In SuperOffice CRM, each contact has a "master switch" for e-marketing on the interests tab. We call this the "e-marketing consent switch".
If the contact has no legal basis for e-marketing emails, the switch is off (gray). If the contact has a legal basis that allows e-marketing, the switch is on (green).
## Choose which contacts to import
When you import SuperOffice CRM contacts into eMarketeer, you can skip or include contacts whose e-marketing switch is off.
* If the checkbox is selected, only contacts with the e-marketing switch on are imported.
* If the checkbox is not selected, all contacts in the selection or project are imported.
## How contacts are identified
Imported contacts are identified in eMarketeer by their primary email address, not by the SuperOffice Contact ID. If the email is not already in eMarketeer, a new contact card is created using that email as the identifier.
Every eMarketeer contact with that email address is updated, and the SuperOffice Contact ID is saved as the contact's External ID. See [How contacts are matched between eMarketeer and SuperOffice](/integrations/superoffice/superoffice-contact-matching.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.emarketeer.com/integrations/superoffice/import-contacts-from-superoffice-crm.md?ask=&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.
