> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/migrate-to-impactcom-from-saasquatch.md).

# 从 SaaSquatch 迁移到 impact.com

当您从 SaaSquatch 迁移到 impact.com 的 Advocate 产品时，您将解锁强大的新功能，并受益于持续改进，因为我们优先发展该产品。impact.com 的团队将为您处理大部分迁移流程，确保您的用户信息、推荐历史、奖励历史、项目设置和模板顺利迁移。以下是您需要做的：

{% stepper %}
{% step %}
**安排迁移**

请联系您的 CSM 以开始。您的 CSM 将与您一起安排迁移开始日期，并指导您了解迁移流程中需要预期的内容。
{% endstep %}

{% step %}
**创建 impact.com 账号**

您需要在 impact.com 平台上创建一个品牌账号。impact.com 的团队将为您提供设置账号所需的说明。

{% hint style="info" %}
**注意：** 请参阅 [从 SaaSquatch 导入推荐计划数据](/brand/zh/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/import-referral-program-data-from-saasquatch.md) 在将用户、奖励或推荐数据导入到您的 impact.com 账号时。
{% endhint %}
{% endstep %}

{% step %}
**查看您的迁移计划**

impact.com 的团队将为您的迁移制定一份量身定制的技术计划，并安排与您的 CSM 的会议以讨论细节。请借此机会向您的 CSM 询问实施所需的预计时间和资源。
{% endstep %}

{% step %}
**开始实施**

在 impact.com 平台上实施任何必要的工具或集成。这可能需要您的技术团队进行开发工作，以确保所有系统正确连接。

1. **切换至 UTT：** impact.com 的 [通用跟踪标签](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/javascript-tag-utt/introduction) 可全面跟踪消费者旅程、直接流量和转化路径，让您从推荐数据中获得有价值的洞察。
2. **更新小部件：** 在您的网站上实施更新后的小部件，以确保无缝集成。
   {% endstep %}
   {% endstepper %}

#### 迁移时间表

迁移时间表取决于您的集成需求，您的 CSM 会在技术计划制定后与您澄清这一点。通常，该过程需要 1-3 周。在此期间，impact.com 的团队会完成必要的后台工作，而您的团队将有时间专注于实施更新。若要估算需要分配给技术团队的时间或资源，请参考您最终确定的技术计划或咨询您的 CSM。


---

# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/migrate-to-impactcom-from-saasquatch.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.