Guidance required: Complete Zoho Cliq to Microsoft Teams migration for 30 users, including historical messages and attachments
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- api
调研方向
The payload names no files, tests or entry points in this SDK; it is a migration support question about Zoho Cliq exports and Microsoft Graph usage. Start by checking whether the questions belong in Microsoft Graph support or Zoho support rather than this repository. Done means a maintainer has routed or answered the questions, not that code has changed.
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe the problem.
Background
We are migrating approximately 30 users from Zoho Cliq to Microsoft Teams using Python, Postman, and Microsoft Graph APIs.
We have successfully created Teams chats and channels and imported some messages. However, the migration is incomplete:
- Our Zoho Cliq organization is currently on the free plan, which displays the message: “Only the recent 7 days data can be exported using the free version of Cliq. Upgrade to our paid plan to export the entire data.”
- The exported message JSON files do not appear to contain the complete historical message history.
- Many message attachments are missing.
- Postman has been unable to download the complete message history.
- Some existing Teams chats and channels have already completed migration mode, so we also need guidance on safely importing the remaining history without duplicating messages.
Questions about Zoho Cliq export
- How can we export the complete historical message history in JSON format from Zoho Cliq, including direct messages, group chats, and channel messages?
- Can the export include the original attachments themselves—such as images, Excel spreadsheets, PDFs, and other documents—or does it provide only attachment metadata or download links?
- Our organization is currently on the Zoho Cliq free plan, which restricts exports to the most recent seven days. Is a subscription upgrade required to export the complete history?
- If an upgrade is required, which Zoho Cliq plan is sufficient for approximately 30 users, and what licensing or subscription level is needed to export all historical messages and attachments?
- Are there any additional export limits, retention restrictions, API permissions, or administrative settings that could prevent a complete export?
- Is there an official Zoho API or supported export method that can retrieve all historical messages and attachments if the administrative export does not provide the complete data?
- We have tried using Postman to retrieve the complete history but have been unsuccessful. What API endpoints, authentication scopes, pagination parameters, and date-range handling should we use, and are there API limitations that prevent retrieving the full history?
Questions about Microsoft Graph and Teams migration
- Can missing historical messages be imported into existing Teams chats and channels after migration mode has already been completed? If not, what is the supported recovery procedure?
- What is the recommended approach for migrating attachments? Can files be uploaded and linked to messages, or are there additional API requirements?
- Are there Microsoft-provided tools, sample projects, or recommended practices for migrating third-party messaging platforms such as Zoho Cliq?
Current implementation
- Source platform: Zoho Cliq, currently on the free plan
- Destination platform: Microsoft Teams
- Scope: Approximately 30 users
- Tools: Python, Postman, and Microsoft Graph REST APIs
- Current state: Teams chats and channels have been created; some message imports are complete
- Main blockers: Complete source-history export, missing attachments, and uncertainty about subscription and API requirements
We need guidance on the supported way to obtain the complete Zoho Cliq export and migrate it into Microsoft Teams without losing historical messages or duplicating content already imported.
Please clarify which questions should be directed to Microsoft Graph/Teams support and which require confirmation from Zoho regarding its subscription and export capabilities.
Describe the solution you'd like.
Awaiting for solution
Additional context?
No response
- 主要语言
- C#
- 星标
- 903
- 派生
- 235
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 26
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoftgraph/msgraph-sdk-powershell 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
microsoftgraph/msgraph-sdk-powershell#3752 ·
维护者通常 2 天内回复
-
status:waiting-for-triage type:bug
难度 4/5 3-5 天 新手友好度 22/100
microsoftgraph/msgraph-sdk-powershell#3822 ·
维护者通常 2 天内回复
-
status:waiting-for-triage type:bug
难度 4/5 3-5 天 新手友好度 48/100
microsoftgraph/msgraph-sdk-powershell#3819 ·
维护者通常 2 天内回复
-
Connect-MgGraph on 2.41 crashes when making a connection with cert, fixes when using 2.39 or lower未关闭status:waiting-for-triage type:bug
难度 4/5 3-5 天 新手友好度 48/100
microsoftgraph/msgraph-sdk-powershell#3816 ·
维护者通常 2 天内回复
-
status:waiting-for-triage type:feature
难度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/msgraph-sdk-powershell#3806 · 5 条评论 · 3 个 reaction ·
维护者通常 2 天内回复
查看 microsoftgraph/msgraph-sdk-powershell 的全部 Issue
相似的 Issue
-
needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
elsa-workflows/elsa-foundation#3130 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
KnifeLemon/Filee#294 ·
维护者通常 1 天内回复
-
good first issue
难度 1/5 1-3 小时 新手友好度 88/100
GlebKievsky/git-tips#4 ·
-
难度 1/5 1 小时以内 新手友好度 77/100
OrchardCMS/OrchardCore#20088 · 1 条评论 ·
维护者通常 1 天内回复