Oracle NetSuite migration guide

Migrate from Oracle NetSuite

Move operational and financial records through NetSuite SuiteTalk REST using a dedicated OAuth 2.0 Integration Record and least-privilege role.

Prerequisites

NetSuite administrator access to enable OAuth 2.0 and REST Web Services.

A NetSuite Integration Record with the Zisyl callback URL.

A role with OAuth 2.0 and read permission for the records being migrated.

The NetSuite account ID, integration client ID, and client secret.

Data coverage

Source records currently supported by the shared migration engine.

Zisyl area	Source records	Migration behavior
People	employee	Employees are mapped by email and invited securely.
CRM	customer, contact, opportunity	Company-scoped duplicate detection preserves relationships.
Projects	job, projectTask	Jobs are imported before dependent project tasks.
Help desk	supportCase	Cases map to tenant tickets with status and requester context.
Calendar	calendarEvent	Meeting dates, location, description, and all-day state are retained.
Accounting	account, vendor, invoice, vendorBill	Codes, totals, tax, balances, and document dates are available for reconciliation.

1. Prepare NetSuite

Enable SuiteTalk REST and create a dedicated migration role.

1Enable OAuth 2.0 and REST Web Services in Company Features.
2Create a least-privilege migration role with REST Web Services permission.
3Create an Integration Record and enable the authorization-code grant.
4Add the callback URL shown by Zisyl and retain the client ID and secret.

2. Connect with OAuth

Save account-specific credentials and authorize a NetSuite user.

1Open Admin → Migration Center and choose Oracle NetSuite.
2Enter the account ID, client ID, and client secret, then save.
3Select Connect NetSuite and approve access using the migration role.
4Return to Zisyl and run Test SuiteTalk.

3. Select and map data

Choose SuiteTalk record types and review field mappings.

1Select only the modules required for the migration.
2Review mappings for custom NetSuite forms and fields.
3Choose duplicate behavior for each data type.
4Start with a conservative per-type record limit.

4. Run a dry run

Read source records and build a durable migration plan without tenant writes.

1Run validation and review inaccessible record types.
2Resolve duplicate customers, projects, vendors, and documents.
3Correct role permissions or mappings and validate again.
4Approve the plan only after totals match the source sample.

5. Migrate and reconcile

Run resumable batches and reconcile operational and financial totals.

1Start the approved migration and monitor progress.
2Verify account codes, customer/vendor balances, and document totals.
3Invite imported users to establish new credentials.
4Use rollback if validation after migration fails.

OAuth tokens and client secrets remain encrypted and server-only.

Passwords, MFA secrets, sessions, and source tokens are never migrated.

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?

Open Zisyl