Zisyl.
Talk to us
Migrations / Zoho One
Zoho One migration guide

Migrate from Zoho One

Authorize Zoho once and migrate across supported Zoho One applications through encrypted, refreshable OAuth access.

Prerequisites

A Zoho One administrator who can approve the requested application scopes.
A Zoho OAuth client configured by the Zisyl superadmin.
The callback URL registered as /api/oauth/zoho/callback on the Zisyl domain.
Tenant admin access to Migration Center.

Data coverage

Source records currently supported by the shared migration engine.

Zisyl areaSource recordsMigration behavior
CRMUsers, Accounts, Contacts, Deals, EventsUsers, customers, contacts, opportunities, and calendar events.
PeopleEmployeesEmployee identity and organization fields.
ProjectsProjects, TasksProjects are imported before task relationships.
DeskTickets, ArticlesHelpdesk tickets and knowledge articles.
BooksChart of Accounts, Contacts, Invoices, BillsAccounts, vendors, invoice balances, and bills.

1. Prepare Zoho OAuth

The platform OAuth client must exist before a tenant can authorize its Zoho organization.

  1. 1In the Zoho API Console, create a server-based OAuth client.
  2. 2Add the exact Zisyl Zoho callback URL.
  3. 3In Superadmin → OAuth, save and enable the Zoho client ID and secret.
  4. 4Do not place tenant access or refresh tokens in environment files.

2. Authorize Zoho One

Tenant admins connect their own organization and approve only the migration scopes.

  1. 1Sign in as a company admin and open Admin → Migration Center.
  2. 2Choose Zoho One and select Connect Zoho.
  3. 3Approve access for CRM, People, Projects, Desk, and Books.
  4. 4If Zoho was connected before migration support was enabled, use Reconnect Zoho once to approve the expanded scopes.

3. Select Zoho applications

Each Zisyl data type is linked to the matching Zoho One application.

  1. 1Select only the applications and record types your organization uses.
  2. 2Review mappings for custom CRM, People, or Books fields.
  3. 3Choose duplicate behavior for each data type.
  4. 4Set a per-data-type limit for a controlled first migration.

4. Validate each module

The dry run can continue when a selected Zoho application is not licensed or accessible.

  1. 1Run validation and review module-level coverage.
  2. 2Unavailable Zoho applications appear as skipped errors in the report rather than terminating the full plan.
  3. 3Reconnect if required scopes are missing.
  4. 4Resolve duplicates and invalid references before migration.

5. Run and reconcile

Records migrate in dependency order while OAuth tokens remain server-side.

  1. 1Start the approved run and monitor batch progress.
  2. 2Verify CRM ownership, project/task relationships, Desk records, and Books balances.
  3. 3Invite migrated users to establish fresh credentials.
  4. 4Roll back the run if validation after migration fails.

Zoho access tokens are refreshed by the shared OAuth service and never exposed to AI or the browser.

A tenant can revoke Zisyl access from Zoho after migration is complete.

Authentication material never migrates

Passwords, password hashes, MFA secrets, sessions, API keys, and OAuth tokens are excluded. Users are matched by email and invited to establish fresh credentials.

Ready to validate your source?

Sign in as a tenant admin and open Admin → Migration Center.

Open Zisyl