Siggly LogoSiggly
Migration Guide

Migrate from Opensense to Siggly

Opensense routes your email through its servers via MX record or connector changes to inject signatures. Siggly achieves the same result without rerouting your mail flow — keeping your email infrastructure cleaner and more secure.

< 4 hrs
Average migration time
100%
Campaign data exportable
99.4%
Successful migrations

Why Teams Migrate from Opensense

No Mail Rerouting

Siggly does not require MX record changes or mail connectors. Your email stays on its native path.

Better Campaign Analytics

Get deeper click and impression analytics with real-time dashboards and exportable reports.

Reduced Security Surface

Eliminating the third-party mail relay removes a potential point of failure and security risk from your email pipeline.

Transparent Pricing

No per-email fees or tiered pricing based on send volume. Siggly uses simple per-user pricing.

Faster Deployment

Deploy signatures without waiting for DNS propagation. Changes take effect in minutes, not hours.

Step-by-Step Migration from Opensense

1

Document DNS & Connector Configuration

Record your current MX records, SPF records, and any Exchange/Google connectors that route mail through Opensense. You will need to revert these during cutover.

2

Export Campaign Data & Templates

Download your Opensense banner campaigns, signature templates, and analytics reports. Save all creative assets.

3

Set Up Siggly & Connect Directory

Create your Siggly workspace and connect your identity provider. Map user fields and set up department-based signature assignments.

4

Recreate Campaigns in Siggly

Import your banner creatives and set up campaign schedules in Siggly's campaign manager. Configure targeting rules by department or region.

5

Pilot & Validate

Deploy Siggly to a pilot group. Confirm that signatures render correctly and campaign tracking links are firing properly.

6

Revert DNS & Remove Opensense Connectors

Update MX records and SPF to remove Opensense from the mail path. Delete the Opensense connectors in Exchange or Google admin. Roll Siggly out to all users.

Pre-Migration Checklist

Screenshot current MX, SPF, and DKIM records
Document all Opensense mail connectors in Exchange or Google
Export all banner campaign creatives and schedules
Download Opensense analytics reports for historical reference
Verify Siggly user sync matches your directory
Plan DNS change window (allow 24-48 hrs for propagation)
Notify email security team about routing changes
"Routing all our email through a third party made our security team nervous. Siggly gave us the same signature injection and campaign tracking without touching our mail flow."

David Okonkwo

VP of IT, Clearwater Financial

Frequently Asked Questions

How do I remove Opensense from my mail flow?
Revert your MX records to point directly to Google or Microsoft, update your SPF record to remove Opensense's include, and delete the inbound/outbound connectors in your admin console.
How long does the DNS change take to propagate?
DNS changes typically propagate within 1-4 hours, though full propagation can take up to 48 hours. Plan your cutover accordingly and keep Opensense active until propagation completes.
Can I run Opensense and Siggly in parallel?
Yes, but only for different user groups. Since Opensense modifies emails in transit, it could conflict with Siggly on the same messages. Segment users during the transition.
What if I need to roll back?
Re-add the Opensense connectors and update your MX/SPF records. Keep your Opensense configuration documented so you can restore it quickly if needed.
Will my campaign tracking data transfer?
Campaign creatives and schedules can be recreated in Siggly. Historical analytics remain in your Opensense account. Export reports before cancelling your subscription.

Start Your Free Migration

Switch to Siggly with zero downtime. Our team helps you every step of the way.