ShipPulse
  • Pricing
  • Docs
  • Blog
  • Compare

Product

TestimonialsChangelogStatus PagesFeedbackRoadmapPricing

Resources

DocsBlogAPI ReferenceSDKHelp Center

Company

AboutContact

Legal

TermsPrivacyCookie PolicyDPASub-processors

Product updates

Changelog updates only. Unsubscribe any time.

ShipPulse operated by Igor Bogdanov, Limassol, Cyprus. [email protected]. Cyprus registration number pending — will be published once issued.

ShipPulse

© 2026 ShipPulse. All rights reserved.

OverviewQuick StartCore ConceptsWidget ReferencePlatform GuidesAPI ReferenceAPI PlaygroundError HandlingPaginationRate LimitingJavaScript SDKWebhooksZapier, n8n & MakeCustom DomainsTeam ManagementBilling & PlansNotification ChannelsAI FeaturesOverviewFrom SenjaFrom Testimonial.toFrom HeadwayFrom Canny

Introduction

  • Overview
  • Quick Start
  • Core Concepts

Embed Widgets

  • Widget Reference
  • Platform Guides

REST API

  • API Reference
  • API Playground
  • Error Handling
  • Pagination
  • Rate Limiting

SDK & Webhooks

  • JavaScript SDK
  • Webhooks
  • Zapier, n8n & Make

Guides

  • Custom Domains
  • Team Management
  • Billing & Plans
  • Notification Channels
  • AI Features

Migrations

  • Overview
  • From Senja
  • From Testimonial.to
  • From Headway
  • From Canny

Need help?

[email protected]
Docs / Migration / Instatus

Migrate from Instatus

Move your status page, uptime monitors, incident history, and subscribers from Instatus to ShipPulse — and get testimonials, changelog, and feedback boards included.

Step 1: Export from Instatus

ShipPulse has a built-in importer for Instatus data:

  1. In Instatus, go to Settings → Export → download your data as JSON.
  2. In your ShipPulse project, go to Status → Import from Instatus.
  3. Upload the JSON file — monitors, incidents, and maintenance windows are imported.

Alternatively, use the Instatus API to export data and our API to re-create records manually.

Step 2: Re-create monitors

If you prefer the API approach, create monitors for each of your services. ShipPulse checks HTTP endpoints every 60 seconds:

curl -X POST https://shippulse.dev/api/v1/monitors \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "API",
    "url": "https://api.yourapp.com/health",
    "method": "GET",
    "check_interval": 60
  }'

Step 3: Import incident history

For each past incident in Instatus, create a corresponding entry in ShipPulse:

curl -X POST https://shippulse.dev/api/v1/incidents \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "API degraded performance",
    "status": "resolved",
    "impact": "minor",
    "body": "We experienced elevated error rates..."
  }'

Step 4: Transfer subscribers

  1. Export subscribers from Instatus (Settings → Subscribers → Export CSV).
  2. Import them via the ShipPulse API — each subscriber can opt in to status updates, changelog emails, or both:
curl -X POST https://shippulse.dev/api/v1/subscribers \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]", "topics": ["status"]}'

Step 5: Update your status page URL

  1. ShipPulse hosts your status page at https://status.shippulse.dev/your-slug by default.
  2. To keep your existing URL (e.g., status.yourapp.com), add a custom domain in ShipPulse → Settings → Domains (Pro plan).
  3. Add a CNAME record pointing to ShipPulse and verify ownership.
  4. Update your website, README, and any external links to point to the new status page URL.

Step 6: Replace the status widget

ShipPulse provides a lightweight embeddable status bar and badge:

<!-- Status bar (shows current system status): -->
<script src="https://cdn.shippulse.dev/widget.js"
        data-project="YOUR_PROJECT_TOKEN"
        data-widget="status-bar">
</script>

<!-- Status badge (icon + uptime %): -->
<script src="https://cdn.shippulse.dev/widget.js"
        data-project="YOUR_PROJECT_TOKEN"
        data-widget="status-badge">
</script>

What you gain by switching

  • Changelog — publish release notes with email notifications and a public changelog page
  • Testimonials — collect and display social proof (replaces a separate tool)
  • Feedback board — public feature requests and roadmap
  • AI incident summaries — auto-draft incident updates from monitoring data
  • All under one subscription vs Instatus' $20–$300/mo plans

White-glove migration included

Email [email protected] with your Instatus export and we'll migrate your monitors, incidents, and subscribers — free for annual subscribers.