finta-upgrade-migration
Handle Finta platform updates and data migration. Trigger with phrases like "finta upgrade", "finta migration".
Best use case
finta-upgrade-migration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Handle Finta platform updates and data migration. Trigger with phrases like "finta upgrade", "finta migration".
Teams using finta-upgrade-migration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/finta-upgrade-migration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How finta-upgrade-migration Compares
| Feature / Agent | finta-upgrade-migration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Handle Finta platform updates and data migration. Trigger with phrases like "finta upgrade", "finta migration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Finta Upgrade & Migration
## Overview
Finta is a fundraising CRM built for founders managing investor pipelines, deal rooms, and investor updates. The API exposes endpoints for funding rounds, investor contacts, and deal room documents. Tracking API changes matters because Finta evolves its data model around fundraising workflows — field renames in round stages, investor contact schema updates, and deal room permission changes can break integrations that sync pipeline data to external analytics or reporting tools.
## Version Detection
```typescript
const FINTA_BASE = "https://api.trustfinta.com/v1";
async function detectFintaApiVersion(apiKey: string): Promise<void> {
const res = await fetch(`${FINTA_BASE}/rounds`, {
headers: { Authorization: `Bearer ${apiKey}`, "Content-Type": "application/json" },
});
const data = await res.json();
const apiVersion = res.headers.get("x-finta-version") ?? "unknown";
console.log(`Finta API version: ${apiVersion}`);
// Check for deprecated fields in round objects
const knownFields = ["id", "name", "stage", "target_amount", "raised_amount", "investors", "created_at"];
if (data.rounds?.[0]) {
const actual = Object.keys(data.rounds[0]);
const deprecated = knownFields.filter((f) => !actual.includes(f));
const added = actual.filter((f) => !knownFields.includes(f));
if (deprecated.length) console.warn(`Removed fields: ${deprecated.join(", ")}`);
if (added.length) console.log(`New fields: ${added.join(", ")}`);
}
}
```
## Migration Checklist
- [ ] Review Finta changelog for breaking changes to round or investor endpoints
- [ ] Audit codebase for hardcoded round stage values (e.g., `"pre-seed"`, `"series-a"`)
- [ ] Verify investor contact schema — check for `firm` vs. `organization` field rename
- [ ] Update deal room document upload endpoint if file size limits changed
- [ ] Test investor update email delivery via API (template format may change)
- [ ] Validate webhook payloads for round status change events
- [ ] Migrate CSV import mappings if column headers were renamed
- [ ] Check OAuth token expiry and refresh behavior for API key rotation
- [ ] Update pipeline stage enum values if Finta added custom stage support
- [ ] Run data export and re-import test to verify round-trip data integrity
## Schema Migration
```typescript
// Finta round schema evolved: flat stage string → structured stage object
interface OldRound {
id: string;
name: string;
stage: string; // "pre-seed", "seed", "series-a"
target_amount: number;
raised_amount: number;
investors: string[]; // investor IDs
}
interface NewRound {
id: string;
name: string;
stage: { key: string; label: string; order: number }; // structured stage
target: { amount: number; currency: string };
raised: { amount: number; currency: string };
investors: Array<{ id: string; committed_amount: number }>;
updated_at: string;
}
function migrateRound(old: OldRound): NewRound {
const stageMap: Record<string, { label: string; order: number }> = {
"pre-seed": { label: "Pre-Seed", order: 1 },
seed: { label: "Seed", order: 2 },
"series-a": { label: "Series A", order: 3 },
};
return {
id: old.id,
name: old.name,
stage: { key: old.stage, ...stageMap[old.stage] ?? { label: old.stage, order: 0 } },
target: { amount: old.target_amount, currency: "USD" },
raised: { amount: old.raised_amount, currency: "USD" },
investors: old.investors.map((id) => ({ id, committed_amount: 0 })),
updated_at: new Date().toISOString(),
};
}
```
## Rollback Strategy
```typescript
class FintaClient {
constructor(private apiKey: string, private version: "v1" | "legacy" = "v1") {}
private get baseUrl(): string {
return `https://api.trustfinta.com/${this.version}`;
}
async getRounds(): Promise<any> {
try {
const res = await fetch(`${this.baseUrl}/rounds`, {
headers: { Authorization: `Bearer ${this.apiKey}` },
});
if (!res.ok) throw new Error(`Finta ${res.status}`);
return await res.json();
} catch (err) {
if (this.version !== "legacy") {
console.warn("Falling back to legacy Finta API");
this.version = "legacy";
return this.getRounds();
}
throw err;
}
}
}
```
## Error Handling
| Migration Issue | Symptom | Fix |
|----------------|---------|-----|
| Stage enum changed | `400 Bad Request` on round creation with old stage value | Fetch current stage options from `/rounds/stages` endpoint |
| Investor schema mismatch | `investors` returns objects instead of string IDs | Update parser to handle both `string[]` and `{id, committed_amount}[]` |
| Deal room permissions | `403 Forbidden` on document upload | Re-check deal room access scopes after API key rotation |
| CSV import column mismatch | Import fails silently with 0 records created | Re-map columns using updated Finta field names from `/schema` endpoint |
| Webhook signature invalid | Webhook verification fails after API update | Update HMAC secret from Finta dashboard settings |
## Resources
- [Finta Changelog](https://www.trustfinta.com/change-log)
- [Finta API Documentation](https://www.trustfinta.com/developers)
## Next Steps
For CI pipeline integration, see `finta-ci-integration`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".