dayrook
Book a walkthrough

Integrations and migration

Check the connections your MSP depends on.

Find your providers, inspect the actions described for each connection, and see which setup or live-test evidence is still needed. Start with the tools you cannot afford to interrupt.

Proposed scope · concept illustration. Review evidence and availability.

Check your integrations Request a migration assessment

Connection health and scope stay visible

On this page2 sections

Integration directory

Check the connection, scope, and evidence status.

Vultr and Cloudflare are platform suppliers. Stripe and SendGrid support billing or communications; they are not general migration sources. Customer integrations are listed by their own supported scope. Status labels distinguish build evidence from a completed live-provider verification.
Microsoft CloudGoogle WorkspaceStripeSendGridQuickBooksXeroVultrCloudflare
  1. 01ConnectPurpose-bound access
  2. 02ScopeCustomer and region
  3. 03ActPolicy and approval
  4. 04ProveRead-back and evidence

14 documented connections · 6 shown

Cloud and identityBuild verified · live tenant proof pendingMicrosoft CloudView documented scope

Route, data, consent, and workflow owners are documented and build-tested; a real customer tenant and deployed provider run still need to be verified for the applicable release.

Documented actions
  • Tenant inventory
  • Policy and compliance review
  • Approved administration
  • SaaS backup and restore
Authentication
  • Microsoft OAuth 2.0 and admin consent
  • GDAP and Microsoft Graph permissions where required
Data-region context
  • Dayrook US or EU customer data region
  • Microsoft provider processing under the connected tenant agreement
Official source: Microsoft Graph overview Reviewed
SaaS backupBuild verified · live tenant proof pendingGoogle WorkspaceView documented scope

Backup, search, restore, and export owners are build-tested; real Google tenant, throttling, archive, and restore evidence remains release-specific.

Documented actions
  • Workload discovery
  • Incremental protection
  • Search and point-in-time restore
  • Alternate restore and export where APIs allow
Authentication
  • Google OAuth 2.0 and administrator consent
Data-region context
  • Dayrook US or EU customer data region
  • Google provider processing under the connected tenant agreement
Official source: Google Workspace developer documentation Reviewed
Billing and accountingSandbox verified · live activation pendingStripeView documented scope

The sandbox platform catalog and reconciliation paths are evidenced; live prices, meters, payments, and customer billing remain subject to the separate production activation review.

Documented actions
  • Subscription and invoice lifecycle
  • Hosted payment and customer portal
  • Usage reconciliation
  • Signed event processing
Authentication
  • Purpose-bound Stripe credential
  • Stripe-signed webhooks with timestamp and replay checks
Data-region context
  • Tenant billing records remain in the selected Dayrook region
  • Stripe processes payment data under its service terms
Official source: Stripe API Reference Reviewed
CommunicationProvider access verified · sender setup pendingSendGridView documented scope

API access has been validated, but sender/domain authentication, templates, inbound routing, and deployed delivery proof remain pending.

Documented actions
  • Transactional email
  • Inbound ticket email
  • Delivery and suppression events
Authentication
  • Purpose-bound SendGrid API credential
  • Signed provider event verification
Data-region context
  • Global provider
  • Tenant records and delivery evidence remain region-bound inside Dayrook
Official source: SendGrid v3 API reference Reviewed
Billing and accountingContract defined · provider proof pendingQuickBooksView documented scope

Connection and webhook contracts are represented in the route catalog; deployed provider authorization, synchronization, and reconciliation evidence is still required.

Documented actions
  • Authorized accounting connection
  • Supported customer and invoice synchronization
  • Reconciliation and exception review
Authentication
  • Provider OAuth callback validation
  • Signed or provider-validated events where supported
Data-region context
  • Dayrook US or EU customer data region
  • Provider processing follows the connected account terms
Official source: QuickBooks Online API getting started Reviewed
Billing and accountingContract defined · provider proof pendingXeroView documented scope

OAuth and webhook standards are documented; deployed provider authorization, synchronization, and reconciliation evidence is still required.

Documented actions
  • Authorized accounting connection
  • Supported customer and invoice synchronization
  • Reconciliation and exception review
Authentication
  • Provider OAuth callback validation
  • Signed or provider-validated events where supported
Data-region context
  • Dayrook US or EU customer data region
  • Provider processing follows the connected account terms
Official source: Xero Developer getting started Reviewed
Browse 8 more documented connections
Platform suppliersRegional foundation active · customer workflow proof pendingVultrView documented scope

US and EU platform infrastructure is provider-recorded; customer-facing infrastructure actions remain limited to the published resource matrix and applicable release evidence.

Documented actions
  • Provider inventory
  • Governed infrastructure plans and applies
  • Regional object storage
  • Provider evidence and drift review
Authentication
  • Purpose-bound provider API credential stored by reference
Data-region context
  • US (ewr)
  • EU (ams)
Official source: Vultr API Reviewed
Platform suppliersActive edge observed · managed proof pendingCloudflareView documented scope

Current read-only Requirements evidence observes active DNS, proxy, TLS, and successful login and chunk probes. Managed and reproducible desired-state reconciliation, the managed-WAF execution rule, and deployed marketing-site QA remain pending.

Documented actions
  • DNS and TLS edge
  • Regional browser and API routing
  • Managed challenge protection
Authentication
  • Scoped Cloudflare API token
Data-region context
  • Global edge
  • Routes customer work toward the selected Dayrook US or EU region
Official source: Cloudflare API Reference Reviewed
MigrationCompany import build verified · live run pendingZendeskView documented scope

The selected-company dry run, source-drift check, import, and target read-back verification are build-tested; a real provider account and deployed regional run remain required.

Documented actions
  • Preview company records
  • Select an approved source snapshot
  • Import and verify companies
Authentication
  • Purpose-bound source credential stored as a Vault reference
Data-region context
  • Import writes only to the selected Dayrook US or EU customer data region
Official source: Zendesk API Reference Reviewed
MigrationCompany import build verified · live run pendingHaloPSAView documented scope

The selected-company dry run, source-drift check, import, and target read-back verification are build-tested; a real provider account and deployed regional run remain required.

Documented actions
  • Preview company records
  • Select an approved source snapshot
  • Import and verify companies
Authentication
  • Purpose-bound source credential stored as a Vault reference
Data-region context
  • Import writes only to the selected Dayrook US or EU customer data region
Official source: HaloPSA API application guide Reviewed
MigrationCompany import build verified · live run pendingZoho DeskView documented scope

The selected-company dry run, source-drift check, import, and target read-back verification are build-tested; a real provider account and deployed regional run remain required.

Documented actions
  • Preview company records
  • Select an approved source snapshot
  • Import and verify companies
Authentication
  • Purpose-bound source credential stored as a Vault reference
Data-region context
  • Import writes only to the selected Dayrook US or EU customer data region
Official source: Zoho Desk API documentation Reviewed
MigrationCompany import build verified · live run pendingJira Service ManagementView documented scope

The selected-company dry run, source-drift check, import, and target read-back verification are build-tested; a real provider account and deployed regional run remain required.

Documented actions
  • Preview company records
  • Select an approved source snapshot
  • Import and verify companies
Authentication
  • Purpose-bound source credential stored as a Vault reference
Data-region context
  • Import writes only to the selected Dayrook US or EU customer data region
Official source: Jira Service Management Cloud REST API Reviewed
Remote supportOptional customer-owned connectionSplashtopView documented scope

The provider may be connected for supported account or inventory context where configured; Dayrook does not claim that these providers launch its native remote sessions.

Documented actions
  • Supported account connection
  • Supported inventory context
Authentication
  • Customer-owned provider credential using the supported connection method
Data-region context
  • Provider processing follows the customer account
  • Dayrook connection metadata follows the selected US or EU region
Official source: Splashtop Open APIs Reviewed
Remote supportOptional customer-owned connectionTeamViewerView documented scope

The provider may be connected for supported account or inventory context where configured; Dayrook does not claim that these providers launch its native remote sessions.

Documented actions
  • Supported account connection
  • Supported inventory context
Authentication
  • Customer-owned provider credential using the supported connection method
Data-region context
  • Provider processing follows the customer account
  • Dayrook connection metadata follows the selected US or EU region
Official source: TeamViewer Web API documentation Reviewed

Questions, answered

Integrations and migration: common questions

Which providers can I connect?

Dayrook covers core MSP categories including Microsoft and Google services, cloud and infrastructure providers, communication tools, identity protocols, and supported security, backup, PSA, and remote-account connections.

Can you migrate an API-backed tool that is not prebuilt?

Where the customer provides sufficient API or export evidence, the migration workflow can discover supported objects, identify gaps, and create a reviewable connector manifest without guessing.

Can I revoke a provider connection?

Target design: Active integrations include a governed lifecycle for testing, health, retry, and revocation, with downstream effects made visible.

Do Splashtop or TeamViewer launch remote sessions from Dayrook?

Those providers can support account connection and inventory where configured. Native Dayrook remote sessions use the governed WebRTC workflow.