Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Guidance required: Complete Zoho Cliq to Microsoft Teams migration for 30 users, including historical messages and attachments

Offen
  • Stimmt etwas nicht?
#3,827 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
api

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

status:waiting-for-triage type:feature
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
  1. How can we export the complete historical message history in JSON format from Zoho Cliq, including direct messages, group chats, and channel messages?
  2. 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?
  3. 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?
  4. 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?
  5. Are there any additional export limits, retention restrictions, API permissions, or administrative settings that could prevent a complete export?
  6. 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?
  7. 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
  1. 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?
  2. What is the recommended approach for migrating attachments? Can files be uploaded and linked to messages, or are there additional API requirements?
  3. 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

Vorherrschende Sprache
C#
Sterne
903
Forks
235
Ø Merge
2 T. 8 Std.
Gemergte PRs (30 T.)
18

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoftgraph/msgraph-sdk-powershell

Alle Issues in microsoftgraph/msgraph-sdk-powershell

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.