instantly-migration-deep-dive
Execute complex Instantly.ai migration strategies for platform changes. Use when migrating between cold email platforms, consolidating workspaces, or re-architecting outreach infrastructure around Instantly. Trigger with phrases like "migrate to instantly", "instantly migration", "switch to instantly", "instantly platform migration", "outreach migration".
What this skill does
# Instantly Migration Deep Dive
## Overview
Strategies for migrating to/from Instantly or consolidating multiple outreach tools into Instantly. Covers data migration (leads, campaigns, templates), account migration (email infrastructure), analytics preservation, and parallel-run strategies with zero-downtime cutover.
## Migration Scenarios
| Scenario | Complexity | Duration |
|----------|-----------|----------|
| Lemlist/Woodpecker/Mailshake to Instantly | Medium | 1-2 weeks |
| Salesloft/Outreach to Instantly | High | 2-4 weeks |
| Multiple Instantly workspaces to one | Low | 1 week |
| Manual outreach to Instantly automation | Low | 3-5 days |
## Instructions
### Step 1: Pre-Migration Audit
```typescript
import { InstantlyClient } from "./src/instantly/client";
const client = new InstantlyClient();
interface MigrationPlan {
sourceLeadCount: number;
sourceCampaignCount: number;
sourceTemplateCount: number;
emailAccountsToMigrate: string[];
estimatedDuration: string;
risks: string[];
}
async function preMigrationAudit(): Promise<MigrationPlan> {
// Check current Instantly workspace state
const existingCampaigns = await client.campaigns.list(100);
const existingAccounts = await client.accounts.list(100);
console.log("=== Current Instantly Workspace ===");
console.log(`Campaigns: ${existingCampaigns.length}`);
console.log(`Accounts: ${existingAccounts.length}`);
// Check warmup status
if (existingAccounts.length > 0) {
const warmup = await client.accounts.warmupAnalytics(
existingAccounts.map((a) => a.email)
);
console.log(`Accounts with warmup: ${(warmup as any[]).length}`);
}
console.log("\n=== Migration Checklist ===");
console.log("[ ] Export leads from source platform (CSV)");
console.log("[ ] Export campaign templates and sequences");
console.log("[ ] Document sending schedules and daily limits");
console.log("[ ] Export analytics/historical data for reference");
console.log("[ ] Identify email accounts to migrate (IMAP/SMTP creds)");
console.log("[ ] Map custom fields to Instantly custom_variables");
console.log("[ ] Create block list from source platform unsubscribes");
console.log("[ ] Plan warmup period (14+ days for new accounts)");
return {
sourceLeadCount: 0, // fill from source audit
sourceCampaignCount: 0,
sourceTemplateCount: 0,
emailAccountsToMigrate: [],
estimatedDuration: "2 weeks",
risks: [
"Warmup period delays campaign launch by 14+ days",
"Custom field mapping may lose data if not 1:1",
"Sending reputation doesn't transfer between platforms",
],
};
}
```
### Step 2: Import Email Accounts
```typescript
// Add email accounts with IMAP/SMTP credentials
async function migrateEmailAccounts(accounts: Array<{
email: string;
first_name: string;
last_name: string;
smtp_host: string;
smtp_port: number;
smtp_username: string;
smtp_password: string;
imap_host: string;
imap_port: number;
imap_username: string;
imap_password: string;
daily_limit: number;
}>) {
const results = { added: 0, failed: 0, errors: [] as string[] };
for (const account of accounts) {
try {
await client.request("/accounts", {
method: "POST",
body: JSON.stringify({
email: account.email,
first_name: account.first_name,
last_name: account.last_name,
smtp_host: account.smtp_host,
smtp_port: account.smtp_port,
smtp_username: account.smtp_username,
smtp_password: account.smtp_password,
imap_host: account.imap_host,
imap_port: account.imap_port,
imap_username: account.imap_username,
imap_password: account.imap_password,
daily_limit: account.daily_limit,
}),
});
results.added++;
console.log(`Added: ${account.email}`);
} catch (e: any) {
results.failed++;
results.errors.push(`${account.email}: ${e.message}`);
}
}
// Enable warmup on all newly added accounts
if (results.added > 0) {
const addedEmails = accounts
.slice(0, results.added)
.map((a) => a.email);
await client.accounts.enableWarmup(addedEmails);
console.log(`Warmup enabled for ${addedEmails.length} accounts`);
}
console.log(`\nAccount migration: ${results.added} added, ${results.failed} failed`);
return results;
}
// Or use OAuth for Google/Microsoft accounts
async function migrateWithOAuth(provider: "google" | "microsoft") {
const endpoint = provider === "google"
? "/oauth/google/init"
: "/oauth/microsoft/init";
const session = await client.request<{ session_id: string; redirect_url: string }>(
endpoint,
{ method: "POST" }
);
console.log(`OAuth flow started. Redirect user to: ${session.redirect_url}`);
console.log(`Session ID: ${session.session_id}`);
// Poll for completion
let status = await client.request(`/oauth/session/status/${session.session_id}`);
console.log("Session status:", status);
}
```
### Step 3: Import Leads from CSV
```typescript
import { readFileSync } from "fs";
import { parse } from "csv-parse/sync";
async function importLeadsFromCSV(
filePath: string,
campaignId: string,
fieldMapping: Record<string, string>
) {
const csv = readFileSync(filePath, "utf-8");
const records = parse(csv, { columns: true, skip_empty_lines: true });
console.log(`Importing ${records.length} leads from ${filePath}`);
const results = { added: 0, skipped: 0, failed: 0 };
for (let i = 0; i < records.length; i++) {
const row = records[i];
try {
const lead: Record<string, unknown> = {
campaign: campaignId,
skip_if_in_workspace: true,
verify_leads_on_import: true,
};
// Map CSV columns to Instantly fields
for (const [csvCol, instantlyField] of Object.entries(fieldMapping)) {
if (row[csvCol]) {
lead[instantlyField] = row[csvCol];
}
}
// Handle custom variables (anything not in standard fields)
const standardFields = ["email", "first_name", "last_name", "company_name", "website", "phone"];
const customVars: Record<string, string> = {};
for (const [csvCol, instantlyField] of Object.entries(fieldMapping)) {
if (!standardFields.includes(instantlyField) && row[csvCol]) {
customVars[instantlyField] = row[csvCol];
}
}
if (Object.keys(customVars).length > 0) {
lead.custom_variables = customVars;
}
await client.request("/leads", {
method: "POST",
body: JSON.stringify(lead),
});
results.added++;
} catch (e: any) {
if (e.message.includes("422")) {
results.skipped++; // duplicate
} else {
results.failed++;
}
}
// Progress report every 100 leads
if ((i + 1) % 100 === 0) {
console.log(`Progress: ${i + 1}/${records.length}`);
}
}
console.log(`Import complete: ${results.added} added, ${results.skipped} skipped, ${results.failed} failed`);
}
// Example field mapping: CSV column -> Instantly field
const mapping = {
"Email": "email",
"First Name": "first_name",
"Last Name": "last_name",
"Company": "company_name",
"Website": "website",
"Title": "title", // goes to custom_variables
"Industry": "industry", // goes to custom_variables
};
```
### Step 4: Migrate Unsubscribes to Block List
```typescript
async function migrateUnsubscribes(unsubscribedEmails: string[]) {
console.log(`Migrating ${unsubscribedEmails.length} unsubscribes to block list`);
// Bulk add to block list
const batchSize = 100;
for (let i = 0; i < unsubscribedEmails.length; i += batchSize) {
const batch = unsubscribedEmails.slice(i, i + batchSize);
await client.request("/block-lists-entries/bulk-create", {
method: "POST",
body: JSON.stringify({ entries: batch }),
});
console.log(`Batch ${Math.floor(i / batchSize) + 1}: ${Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.