Migration Guide

Migrate from Letsignit to Siggly

Letsignit integrates with Microsoft 365 for signature and banner campaign management. Siggly offers broader platform support, more design flexibility, and an analytics dashboard that gives marketing teams actionable insights.

< 2 hrs
Average migration time
100%
Templates transferable
99.6%
Successful migrations

Why Teams Migrate from Letsignit

Multi-Platform Support

Letsignit focuses on Microsoft 365. Siggly supports Google Workspace, M365, and hybrid environments equally well.

Advanced Template Editor

Build signatures with a true drag-and-drop editor. Add conditional content, dynamic banners, and custom HTML blocks.

Actionable Analytics

Move beyond basic click counts. Siggly shows conversion paths, department comparisons, and campaign ROI estimates.

Better Value

Get all features at every pricing tier. No need to upgrade for campaign management or analytics access.

Step-by-Step Migration from Letsignit

1

Audit Letsignit Configuration

Review your Letsignit signature rules, campaign schedules, and Azure AD integration settings. Note which groups or OUs have specific templates assigned.

2

Export Templates & Campaign Assets

Copy signature HTML from the Letsignit editor. Download all banner images, campaign schedules, and any custom CSS.

3

Configure Siggly Workspace

Connect Siggly to Azure AD or Google Workspace. Set up the same group-based assignments you used in Letsignit.

4

Rebuild Signatures & Campaigns

Import your templates into Siggly's editor. Set up banner campaigns with the same creatives and scheduling rules.

5

Deploy to Pilot Group & Test

Push Siggly to a small team. Verify signatures render correctly in Outlook desktop, OWA, Outlook mobile, and any other clients your org uses.

6

Disable Letsignit & Go Live

Remove the Letsignit app from Azure AD Enterprise Applications. Deploy Siggly to all users and cancel your Letsignit subscription.

Key Considerations for Letsignit Migrations

Letsignit stores its configuration as an Azure AD Enterprise Application. When you disable it, all Letsignit-managed signatures stop updating. Make sure Siggly is fully deployed before removing the Letsignit app registration.

If you rely on Letsignit's banner campaign scheduling, map out your active and upcoming campaigns before starting the migration. Siggly's campaign manager supports date-based scheduling, audience targeting, and A/B testing, so you can replicate (and improve upon) your existing setup.

Teams that used Letsignit's internal communication banners will find Siggly's campaign system familiar but more powerful. You can target by department, region, or custom user attributes, and the analytics dashboard shows real-time performance rather than end-of-day summaries.

"Letsignit only worked well with M365. When we added Google Workspace for a subsidiary, we needed something cross-platform. Siggly handled both tenants from one dashboard."

Isabelle Moreau

IT Manager, Pinnacle Industries

Frequently Asked Questions

How do I remove Letsignit from Azure AD?
Go to Azure Portal > Azure Active Directory > Enterprise Applications, find Letsignit, and delete the application. This removes its ability to manage signatures.
How long does migration from Letsignit take?
Most organizations complete the migration in 1-2 hours. Complex campaign setups may take slightly longer to recreate.
Can I run both tools at the same time?
Yes, temporarily. Letsignit and Siggly can coexist during the transition since they manage signatures through different mechanisms. Deploy Siggly to a test group first.
What happens to my campaign history?
Campaign performance data stays in your Letsignit account. Export reports before cancelling. Siggly starts tracking from the moment you deploy.
Is training required?
End users need no training. Admins familiar with Letsignit will find Siggly's interface intuitive — most are productive within 20 minutes.

Start Your Free Migration

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