---
title: "Mailchimp to Dynamics 365 Migration | FlitStack AI"
description: "Migrate Mailchimp to Dynamics 365 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/mailchimp/to/dynamics-365-sales"
---

# Mailchimp to Dynamics 365 migration

We migrate Mailchimp Audiences, Contacts, Tags, and campaign engagement history into Microsoft Microsoft Dynamics 365 Sales , preserving subscriber status flags as custom fields, resolving Audience-to-Account splits, and documenting every automation requiring rebuild in the destination before any data moves.

Short answer

FlitStack AI migrates account + marketing list or custom entities, lead or contacts, accounts, multi-select picklist or custom fields and custom criteria or marketing lists from Mailchimp to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/mailchimp/to/dynamics-365-sales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Mailchimp ![](https://flitstack.ai/platforms-trim/mailchimp.webp)

Destination Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Account + Marketing List or Custom Entity Lead or Contact Account Multi-Select Picklist or Custom Field Custom Criteria or Marketing List

Mapped field by field · sample run · one-click rollback

## What moves from Mailchimp to Dynamics 365?

Moving from Mailchimp to Microsoft Microsoft Dynamics 365 Sales is a data-model migration across fundamentally different platforms: Mailchimp organizes around Audiences and subscriber status for email campaigns, while Microsoft Dynamics 365 Sales organizes around Leads, Contacts, Accounts, and Opportunities for sales pipeline management.

Read the full summary

We migrate Contacts as Leads (for unverified prospects) or Contacts tied to Accounts (for known buyers), preserve each contact's Mailchimp status (subscribed, unsubscribed, non-subscribed, cleaned) in a custom field on the Dynamics record, and import Tags as multi-select picklists or custom fields. Mailchimp campaign metadata (subject, send date, recipient count, open and click rates) migrates as Activity notes or a custom Campaign Engagement entity so the sales team can see marketing touch history. We do not migrate Automations (Mailchimp's workflow engine stores logic in a proprietary format with no export path), and we do not migrate email Templates because Mailchimp's block syntax does not render in Dynamics. We deliver a written inventory of every active automation and its recommended Microsoft Dynamics 365 Sales equivalent so the customer's admin rebuilds them in Power Automate or Sales Hub.

1:N split

### Audience → Account + Marketing List or Custom Entity

Mailchimp Audiences have no direct single-object equivalent in Microsoft Dynamics 365 Sales .

How it maps

We create a top-level Account record named for the Audience (using Audience name as the Account name), then create Dynamics Marketing List members linked to that Account, preserving the Audience's opt-in workflow settings. For organizations with multiple distinct Audiences representing different business lines, each Audience maps to a separate Account and Marketing List pair.

1:N split

### Contact → Lead or Contact

Mailchimp Contacts with a confirmed company affiliation and a buyer-role email address (procurement, executive, sales-rep domains) map to a Dynamics Contact tied to the Account derived from their Audience.

How it maps

Contacts with personal or unqualified email domains with no company affiliation map to a Dynamics Lead for sales follow-up. The original Mailchimp status (subscribed, unsubscribed, non-subscribed, cleaned) is preserved in a custom field mc\_original\_status\_\_c on both Lead and Contact.

1:1

### Company (stored in Mailchimp merge fields) → Account

If Contacts carry a company name via a Mailchimp merge field (typically named COMPANY or COMPANY\_NAME), we resolve each unique company name to a Dynamics Account record.

How it maps

Account is created before Contact import so that the Contact-to-Account Lookup is satisfied at insert time. Company names that are blank or non-specific in Mailchimp create placeholder Accounts that the customer's admin reconciles post-migration.

configuration

### Tag → Multi-Select Picklist or Custom Field

Mailchimp tags migrate as custom fields on the Dynamics Lead or Contact object.

How it maps

If fewer than 150 distinct tag values exist across the contact base, we use a multi-select picklist field named mc\_tags\_\_c. For tag volumes exceeding picklist limits, we create a related custom entity mc\_contact\_tag\_\_c with a Lookup to Contact/Lead and a Tag Name field, allowing an N:N relationship without picklist constraints.

mapping

### Segment → Custom Criteria or Marketing List

Mailchimp segments are dynamic filter sets (based on merge field values, tag presence, engagement history, or signup date) that do not export in a form compatible with Dynamics 365.

How it maps

We export segment rules as structured JSON describing the filter conditions and flag count, then create equivalent Dynamics Marketing List membership criteria or Power Automate flows that replicate the segment logic. Complex behavioral segments (based on opens, clicks, purchase recency) require a rebuild in Dynamics Customer Insights or a connector like Marketing4Dynamics.

mapping

### Campaign → Campaign + CampaignMember

Mailchimp campaign metadata (campaign name, subject line, send date, recipient count, open rate, click rate, bounce rate, unsubscribe count) migrates as a Dynamics 365 Campaign record with metrics stored in custom fields.

How it maps

Individual contact engagement with each campaign (opened, clicked, bounced, unsubscribed) migrates as CampaignMember records with corresponding statuses. We import the last 90 days of campaign history by default; full history requires pagination across multiple Mailchimp API pages.

******What moves 10 objects

Mailchimp Dynamics 365

- Audience Account split
- Contact Lead or Contact split
- Company Account 1:1
- Tag Multi-Select Picklist or Custom Field transformed
- Segment Custom Criteria or Marketing List transformed
- Campaign Campaign transformed

\+ 4 more in the mapping below

## How Mailchimp and Dynamics 365 differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension              | Mailchimp                                                                                    | Dynamics 365                                                                                                                         |
| ---------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Data model purpose     | Email marketing database organized around Audiences and subscriber status                    | Sales CRM organized around Leads, Contacts, Accounts, and Opportunities for pipeline management                                      |
| Contact vs. Lead model | Single Contact record within an Audience with status flags                                   | Separate Lead (unqualified) and Contact+Account (qualified) records with explicit Convert action                                     |
| Pricing model          | Contact-count billing across all Audiences including unsubscribed and non-subscribed records | Per-user licensing with a 5-seat minimum on Sales Professional                                                                       |
| Automation engine      | Customer Journeys with trigger-based branching, gated at 5-step limit on Standard tier       | Power Automate and Sales Hub workflows, available from Professional tier without step-count limits                                   |
| Email sending          | Native email sending with deliverability infrastructure built in                             | No native sending in Sales Hub; requires Dynamics 365 Marketing, Customer Insights, or third-party connector like Marketing4Dynamics |
| Campaign tracking      | Opens, clicks, bounces, and unsubscribes tracked per contact with aggregate reporting        | Campaign and CampaignMember objects track marketing interactions; analytics require additional configuration                         |
| Minimum user count     | Free tier available at up to 500 contacts; no minimum user requirement                       | Sales Professional minimum 5 users; Enterprise minimum 5 users; adds licensing overhead for small teams                              |

## What to watch for in a Mailchimp to Dynamics 365 migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Microsoft Dynamics 365 Sales has no native email sending

Microsoft Dynamics 365 Sales tracks email interactions but does not send marketing emails natively.

How we handle it

Organizations migrating from Mailchimp expect to manage email campaigns inside the CRM, but Microsoft Dynamics 365 Sales requires either Dynamics 365 Marketing (separate product, separate cost), Customer Insights Journeys, or a third-party connector like Marketing4Dynamics to send email from the platform. We migrate contact and engagement data into Dynamics, but the customer's email sending strategy must be addressed separately. Many teams run Microsoft Dynamics 365 Sales for pipeline management and keep Mailchimp (or migrate to Klaviyo, ActiveCampaign, or Marketing Cloud) for actual email execution.

high

### Mailchimp subscriber status has no direct Dynamics equivalent

Mailchimp tracks subscriber status at the record level (subscribed, unsubscribed, non-subscribed, cleaned) which determines both deliverability and billing.

How we handle it

Microsoft Dynamics 365 Sales has a HasOptedOutOfEmail field on Contact/Lead and a DoNotBulkPostalMail field, but these do not capture the full Mailchimp status taxonomy. We preserve the original Mailchimp status in a custom field mc\_original\_status\_\_c on every migrated Lead and Contact. The customer's admin configures Dynamics field security and routing rules based on this field after migration. Skipping this step means unsubscribed and cleaned records may re-enter email campaigns in Dynamics, creating compliance risk.

medium

### Contact count billing vs. per-user licensing creates cost misalignment

Mailchimp bills based on total contacts including unsubscribed and non-subscribed records; Microsoft Dynamics 365 Sales bills per user with a 5-user minimum on Professional ($95/user/month) and Enterprise ($165/user/month).

How we handle it

Teams that chose Mailchimp for its free tier at 500 contacts may face a significant cost increase moving to Dynamics because the minimum 5-user floor applies regardless of contact volume. We flag this during scoping and recommend the customer evaluate whether Microsoft Dynamics 365 Sales Professional or a lighter Dynamics 365 Essentials configuration meets their needs before migration begins.

medium

### Automations and Customer Journeys cannot migrate as code

Mailchimp's automation engine (Welcome emails, abandoned cart, birthday, post-purchase, and custom Customer Journeys) stores workflow logic in a proprietary format with no export mechanism.

How we handle it

Microsoft Dynamics 365 Sales does not have an equivalent automation engine natively; workflow automation requires Power Automate (a separate product) or Dynamics 365 Marketing journeys. We do not migrate automations as executable code. We deliver a written inventory of every active Mailchimp automation with its trigger conditions, step count, enrollment size, and recommended Power Automate or Dynamics 365 Marketing rebuild approach. The customer's admin or a Power Automate specialist rebuilds them post-migration.

medium

### Data quality gaps from Mailchimp's address field limitations

Mailchimp's contact address structure (address line 1, line 2, city, state, postal code, country) does not map directly to Dynamics' postal address model, which separates address purposes (billing, shipping, other) with individual address fields per purpose.

How we handle it

Many Mailchimp contacts have incomplete or inconsistent address data (missing state, non-standard city formatting, free-form address text in a single field). We profile address completeness during the data assessment phase and flag records that require address verification or standardization before import. Fusion5's Dynamics migration guide confirms that 'mixing up date formats, mishandling special characters, or neglecting de-duplication of customer records' are common errors that undermine CRM reporting.

## How the migration runs

1. ### Source audit and scope definition

   We audit the Mailchimp account across all Audiences, contact counts (breaking down subscribed, unsubscribed, non-subscribed, and cleaned records separately), tag volumes, active automations, e-commerce connection status, and campaign history depth.

   What this step covers

   We also identify Mailchimp merge fields, segment definitions, and any connected e-commerce stores (Shopify, WooCommerce). The output is a written migration scope that confirms which data types are in scope, which are excluded, and an estimated contact-to-Lead versus Contact split ratio based on company affiliation and email domain analysis.

2. ### Dynamics environment preparation and schema design

   We review the target Microsoft Dynamics 365 Sales environment for existing entities, security roles, and field-level security.

   What this step covers

   We create the custom fields needed (mc\_original\_status\_\_c, mc\_engagement\_type\_\_c, mc\_tags\_\_c or related entities, campaign metrics fields), configure Dynamics Marketing Lists if the customer uses marketing list-based segmentation, and verify the minimum 5-user license count. If the customer plans to use Dynamics 365 Marketing or Customer Insights for email sending post-migration, we note the additional configuration requirements during this phase.

3. ### Data profiling and quality cleansing

   We run a data quality assessment across all Mailchimp contacts: flagging duplicates (matching on email address), identifying records with blank required fields, profiling address completeness, and analyzing tag distribution to determine whether a multi-select picklist or custom tag entity is the right approach.

   What this step covers

   We apply de-duplication logic (keeping the most recently updated record for each email address) before migration. Data cleansing tools are applied at this stage for bounced email addresses and records with invalid formats. Fusion5's Dynamics migration guidance recommends involving business users to validate sample legacy data before committing to field mappings.

4. ### E-commerce data export and account resolution

   If the Mailchimp account has an active e-commerce integration (Shopify, WooCommerce, or other), we export order and product data first while the connection remains live.

   What this step covers

   We resolve company names from Mailchimp contacts to Dynamics Accounts, creating each unique company as an Account record before contact import begins. This Account-first approach ensures that Contact-to-Account Lookups are satisfied at insert time and avoids orphaned Contact records with no Account association.

5. ### Contact migration with status preservation

   We import Contacts into Dynamics 365 in dependency order: Accounts first, then Leads (for unqualified contacts without company affiliation), then Contacts (for qualified contacts with a matched Account).

   What this step covers

   Each record carries the mc\_original\_status\_\_c custom field preserving the original Mailchimp status. Tags migrate as either mc\_tags\_\_c multi-select picklist values or as mc\_contact\_tag\_\_c related records depending on volume. After contact import completes, we run a row-count reconciliation report comparing Mailchimp contact counts by status against Dynamics Lead and Contact counts, resolving any discrepancies before proceeding.

6. ### Campaign and engagement history migration

   We import Mailchimp campaign metadata as Dynamics Campaign records, then import individual contact engagement events (opens, clicks, bounces, unsubscribes) as Task records linked to the corresponding Campaign and Contact.

   What this step covers

   The activity timeline preserves the original event timestamp. After import, we reconcile campaign-level metrics (total sends, open rate, click rate) against the Mailchimp report summary to confirm data accuracy. We note that Dynamics native campaign reporting requires additional configuration; the customer may need Power BI or Dynamics reports for the level of analytics previously available in Mailchimp.

7. ### Cutover, validation, and automation rebuild handoff

   We freeze Mailchimp writes during cutover, run a final delta migration of any contacts or engagement events modified during the migration window, then set Microsoft Dynamics 365 Sales as the system of record.

   What this step covers

   We deliver the automation inventory document listing every active Mailchimp automation with its trigger, step count, and recommended Power Automate rebuild approach. We provide a one-week hypercare window for reconciliation issues. We do not rebuild Mailchimp automations as Power Automate flows or Dynamics 365 Marketing journeys inside the migration scope; that work is a separate engagement.

![](https://flitstack.ai/platforms/mailchimp.svg) Mailchimp ![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Dynamics 365 Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**7-11 weeks** Large or heavily customised accounts

A quote scales with contact volume, Audience complexity, and whether e-commerce data requires a custom entity structure in Dynamics. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Mailchimp to Dynamics 365 →](https://flitstack.ai/contact)

## Why teams move from Mailchimp to Dynamics 365

- Teams that scale beyond Mailchimp's contact-count pricing hit a structural ceiling. As Audience sizes grow, monthly Mailchimp costs increase with every subscribed and unsubscribed record. Microsoft Microsoft Dynamics 365 Sales uses per-user licensing that becomes more predictable and cost-effective at scale, particularly for organizations with a high ratio of marketing contacts relative to active sales seats.
- Organizations with an established sales process need Lead and Contact management with pipeline tracking that Mailchimp cannot provide. Reddit discussions on r/CRM and r/MarketingAutomation document teams using Mailchimp as a de facto contact database but hitting its limits when sales reps need to track deal stages, account hierarchies, and multi-user collaboration on Opportunities.
- Post-Intuit acquisition (2021), Mailchimp's product roadmap has drawn criticism from long-term users on Reddit and G2, with reviewers characterizing platform investment as stagnant and direction uncertain. Teams committed to the Microsoft ecosystem for productivity, ERP, and security compliance move to Microsoft Dynamics 365 Sales to consolidate their business application stack under a single vendor with enterprise support agreements.
- Microsoft 365 Copilot integration gives Microsoft Dynamics 365 Sales AI capabilities that Mailchimp does not match. Microsoft's 2025 announcements extend Copilot directly into Outlook, Teams, and the CRM record view, allowing sales reps to query Opportunity status, draft follow-up emails, and surface customer context without leaving their inbox. Organizations already committed to Microsoft 365 can activate these capabilities within an existing tenant.
- Microsoft Dynamics 365 Sales provides native pipeline forecasting, territory management, and quote-to-cash workflows that require third-party extensions or are unavailable entirely in Mailchimp. G2 reviews of Microsoft Dynamics 365 Sales cite pipeline visibility, advanced forecasting, and integration with the broader Microsoft ecosystem (Power BI, Teams, SharePoint) as drivers for organizations moving beyond email marketing into full sales process management.

Questions, answered

## Mailchimp to Dynamics 365 migration questions

How long does a Mailchimp to Microsoft Dynamics 365 Sales migration take?

Most migrations land between three and five weeks for accounts under 10,000 Contacts with one or two Audiences and no e-commerce data. Migrations with multiple Audiences, campaign engagement history, e-commerce orders from a connected Shopify store, or tag structures requiring a custom tag entity move to seven to eleven weeks because of data profiling time, Address cleansing, and engagement reconciliation. Discovery and scoping adds one to two weeks before migration begins.

Can we keep Mailchimp for email marketing after migrating to Microsoft Dynamics 365 Sales ?

Yes. This is one of the most common migration patterns. Many organizations move their contact and account data into Microsoft Dynamics 365 Sales for pipeline management while keeping Mailchimp for email campaign execution. We migrate the contact records and engagement history into Dynamics so the sales team has full visibility; Mailchimp continues as the sending platform with Dynamics as the CRM of record. A bidirectional connector like Marketing4Dynamics can be configured post-migration to sync new Dynamics Leads and Contacts back into Mailchimp Audiences for ongoing marketing.

Do Mailchimp Automations and Customer Journeys migrate to Dynamics 365?

No. Mailchimp's automation engine stores workflow logic (triggers, delays, conditions, actions) in a proprietary format that has no export mechanism. Microsoft Dynamics 365 Sales does not have a native equivalent automation engine; workflow automation requires Power Automate or Dynamics 365 Marketing. We do not migrate automations as executable code. We deliver a written inventory of every active Mailchimp automation with its trigger type, enrollment count, step sequence, and recommended Power Automate or Dynamics 365 Marketing Journey rebuild approach. The customer's admin or a Microsoft partner rebuilds them post-migration.

What happens to Mailchimp's subscriber status after migration?

Mailchimp subscriber status (subscribed, unsubscribed, non-subscribed, cleaned) has no direct Microsoft Dynamics 365 Sales equivalent. We preserve the original status in a custom field mc\_original\_status\_\_c on every migrated Lead and Contact. The customer's admin configures field-level security and routing rules based on this field after migration. For example, unsubscribed and cleaned records can be flagged for exclusion from email campaigns in Dynamics or in the customer's email sending platform of choice.

Can we migrate Mailchimp campaign open and click history into Dynamics 365?

Yes. We migrate Mailchimp campaign metadata (subject, send date, recipient count) as Dynamics Campaign records and individual contact engagement events (opens, clicks, bounces, unsubscribes) as Task records linked to the Campaign and the Contact. Open and click timestamps are preserved in the Task ActivityDate field. Note that Dynamics native campaign analytics require additional configuration; customers accustomed to Mailchimp's out-of-the-box reporting should plan to configure Power BI dashboards or Dynamics native reports post-migration.

What data does NOT migrate from Mailchimp to Microsoft Dynamics 365 Sales ?

Automations and Customer Journeys do not migrate as executable code. Email Templates do not migrate because Mailchimp's block syntax does not render in Dynamics; we export HTML files for reference and the customer rebuilds templates in Dynamics or their chosen email platform. Archived, cleaned, and deleted contacts do not export from Mailchimp. E-commerce data requires the connected store to remain live during export; if severed before migration completes, historical order data may be inaccessible. Workflows, sequences, landing pages, forms, and Mailchimp's GDPR consent logs do not migrate.

Do we need a minimum number of Microsoft Dynamics 365 Sales users for this migration?

Yes. Microsoft requires a minimum of 5 user licenses for Microsoft Dynamics 365 Sales Professional ($95/user/month) and Microsoft Dynamics 365 Sales Enterprise ($165/user/month). Teams that chose Mailchimp for its free tier at up to 500 contacts may face a significant cost increase moving to Dynamics. We flag this during scoping and recommend the customer evaluate whether the 5-user minimum is justified by their sales team size before committing to migration. Dynamics 365 Teams (limited functionality) or a lighter Microsoft 365 Business plan may be a better fit for smaller teams.

## Related migrations

[![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp) Migrate to **Dynamics 365** Every source we move into Dynamics 365, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/dynamics-365-sales)

### [Dynamics 365 implementation](https://flitstack.ai/services/dynamics-365-implementation)

[Set up Dynamics 365 and migrate into it as one engagement.](https://flitstack.ai/services/dynamics-365-implementation)

[See the service →](https://flitstack.ai/services/dynamics-365-implementation) [**Zoho CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zoho-crm/to/dynamics-365-sales) [**Odoo CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/odoo-crm/to/dynamics-365-sales) [**HubSpot to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/dynamics-365-sales) [**Salesforce to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/dynamics-365-sales) [**Copper to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/copper/to/dynamics-365-sales) [**Convertkit to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/convertkit/to/dynamics-365-sales) [**Mailchimp to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/salesforce-sales-cloud) [**Mailchimp to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot) [**Mailchimp to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/zoho-crm)

## Sources: official documentation

1. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
2. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
3. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
4. [Execute Batch Operations on Dataverse — Microsoft Learn](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api)
5. [Merge Fields Documentation — Mailchimp Developer](https://mailchimp.com/developer/marketing/docs/merge-fields/)
6. [Format Guidelines for Your Import File — Mailchimp](https://mailchimp.com/help/format-guidelines-for-your-import-file/)
7. [Manage Audience and Signup Form Fields — Mailchimp](https://mailchimp.com/help/manage-audience-signup-form-fields/)

Get a quote

## Moving from Mailchimp to Dynamics 365?

Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
