Migration Guide

Migrate from CodeTwo to Siggly

CodeTwo requires on-premise agents or Azure service installations to manage signatures. Siggly is 100% cloud-native — no agents, no server maintenance, no infrastructure overhead.

< 3 hrs
Average migration time
100%
Template designs preserved
99.5%
Successful migrations

Why Teams Migrate from CodeTwo

No Agents to Install

Eliminate on-premise server agents entirely. Siggly runs in the cloud and requires zero local infrastructure.

Template Import

Bring your CodeTwo signature designs into Siggly. Export your HTML and re-import it into our drag-and-drop editor.

Active Directory Sync

Siggly syncs with Azure AD and on-prem AD via Microsoft Graph, preserving all user attribute mappings from CodeTwo.

Automatic Updates

No more patching on-prem agents. Siggly updates automatically and is always on the latest version.

Step-by-Step Migration from CodeTwo

1

Inventory CodeTwo Components

Identify all CodeTwo components: on-premise agents, Exchange rules, Azure tenant app registrations, and any CodeTwo cloud connectors.

2

Export Signature Templates

Open the CodeTwo admin panel and export each signature template as HTML. Download all associated images, logos, and banner files.

3

Set Up Siggly Cloud Workspace

Create your Siggly workspace, connect it to Azure AD or Google Workspace, and verify user sync is pulling the correct attributes.

4

Import & Rebuild Templates

Paste your CodeTwo HTML into Siggly's editor. Remap dynamic placeholders (e.g., {firstname}, {title}) to Siggly's field syntax.

5

Test with a Pilot Department

Assign Siggly signatures to a single department while CodeTwo continues handling the rest. Confirm rendering on desktop, web, and mobile clients.

6

Uninstall CodeTwo Agents & Go Live

After successful validation, remove CodeTwo agents from your servers, delete the Azure app registration, and disable any Exchange rules CodeTwo created. Roll Siggly out org-wide.

What You Gain After Switching

Zero Server Maintenance

Stop patching, monitoring, and troubleshooting on-premise signature agents. Siggly runs entirely in the cloud.

Lower Infrastructure Costs

Eliminate the server resources CodeTwo agents consume. Reduce your IT overhead immediately.

Real-Time Signature Analytics

Get visibility into signature impressions, link clicks, and banner campaign performance — data CodeTwo does not provide.

Manage From Anywhere

Administer signatures from any browser. No VPN or RDP into on-prem servers needed.

"Uninstalling the CodeTwo agent from our Exchange server felt like lifting a weight. Siggly gave us the same control with none of the maintenance headaches."

Rafiq Anwar

Systems Administrator, NovaTech Solutions

Frequently Asked Questions

How do I export templates from CodeTwo?
In the CodeTwo admin panel, open each signature rule and use the HTML editor view to copy the template source. Save images from the embedded assets folder.
How long does migration from CodeTwo take?
Typically 2-3 hours. Organizations with multiple on-prem agents or complex rule trees may need half a day. Our migration team offers guided sessions.
Can I keep CodeTwo running during the transition?
Absolutely. CodeTwo and Siggly can operate side by side. CodeTwo continues handling signatures for users not yet migrated to Siggly.
What if something goes wrong — can I revert?
Yes. Keep your CodeTwo agents installed (but inactive) during the first week. If you need to roll back, simply re-enable the CodeTwo service and disable Siggly deployment.
Will my team need training?
End users see no change — signatures are applied automatically. Admins typically complete Siggly onboarding in under 30 minutes with our interactive walkthrough.

Start Your Free Migration

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