Guidance required: Complete Zoho Cliq to Microsoft Teams migration for 30 users, including historical messages and attachments
Les mainteneurs répondent en général sous 2 jours
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 8/100
- Type d'issue
- Fonctionnalité
- Clarté
- À clarifier
- Activité
- Active
- Domaine
- api
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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
- Langage dominant
- C#
- Étoiles
- 901
- Forks
- 232
- Merge moyen
- 2 j 1 h
- PR mergées (30 j)
- 26
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoftgraph/msgraph-sdk-powershell
-
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
microsoftgraph/msgraph-sdk-powershell#3752 ·
Les mainteneurs répondent en général sous 2 jours
-
status:waiting-for-triage type:bug
Difficulté 4/5 3-5 jours Accessibilité débutants 22/100
microsoftgraph/msgraph-sdk-powershell#3822 ·
Les mainteneurs répondent en général sous 2 jours
-
Microsoft.Graph.Authentication dependency Microsoft.Graph.Authentication.Loader.dll is unsignedOuvertestatus:waiting-for-triage type:bug
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
microsoftgraph/msgraph-sdk-powershell#3819 ·
Les mainteneurs répondent en général sous 2 jours
-
Connect-MgGraph on 2.41 crashes when making a connection with cert, fixes when using 2.39 or lowerOuvertestatus:waiting-for-triage type:bug
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
microsoftgraph/msgraph-sdk-powershell#3816 ·
Les mainteneurs répondent en général sous 2 jours
-
Supported way to get the tokenOuvertestatus:waiting-for-triage type:feature
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
microsoftgraph/msgraph-sdk-powershell#3806 · 4 commentaires · 3 réactions ·
Les mainteneurs répondent en général sous 2 jours
Toutes les issues de microsoftgraph/msgraph-sdk-powershell
Issues similaires
-
status:waiting-for-triage type:bug
Difficulté 1/5 Moins d'une heure Accessibilité débutants 84/100
microsoftgraph/msgraph-sdk-dotnet#3194 ·
Les mainteneurs répondent en général sous 1 jour
-
Backend enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
Les mainteneurs répondent en général sous 1 jour
-
UI: money shows the minus sign next to the number, not before the currency (IL -3.0m, not -IL 3.0m)Ouvertearea: sim area: unity enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
eyalgolan/statecraft-israel#1107 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
dimitar-radenkov/Pointframe#271 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
qew21/Genshin-Subtitles#45 ·