Migrate from Panacea to HubSpot

Panacea workflow and automation definitions do not migrate to HubSpot's workflow builder

Panacea's workflow engine, project rules, and sequence logic are source-platform constructs with no stored representation that transfers to HubSpot's automation system. HubSpot's workflow builder operates on triggers, conditions, and actions defined within HubSpot's own data model. FlitStack AI migrates data only — every automation, sequence, and rule must be rebuilt from scratch in HubSpot. We can export Panacea workflow definitions as a reference document for your HubSpot admin, but the migration does not carry forward any active logic.

HubSpot lifecycle_stage is a contact-level property that drives HubSpot's marketing-contact billing model

HubSpot bills based on the number of marketing contacts in your portal, and the lifecycle_stage property determines whether a contact counts as a marketing contact. Migrated contacts default to no lifecycle stage unless explicitly set during import. Teams moving from Panacea's flat contact model need to decide on a lifecycle-stage assignment strategy upfront — setting all migrated contacts to 'customer' immediately triggers marketing-contact billing for the full imported set. FlitStack AI surfaces this before import and allows you to defer lifecycle assignment to a post-migration review step.

N-to-N contact-company associations in Panacea require de-normalization into HubSpot's primary-lookup model

Panacea supports multiple company associations per contact through a separate association table. HubSpot contacts have one primary CompanyId lookup — secondary company associations are stored as a secondary association object, not a first-class field. During migration, FlitStack AI sets the most-recently-modified company as the primary CompanyId and adds remaining companies as HubSpot secondary Company Associations. The association role metadata from Panacea is preserved in a custom property on the association so your team can reconstruct the full picture after migration.

Panacea custom objects require HubSpot custom object schema creation before data writes

HubSpot custom objects are Enterprise-tier features that must be explicitly created in the account before any data can be imported into them. Unlike standard objects (Contact, Company, Deal) which accept data immediately, custom object migration requires a schema-creation step in HubSpot — defining the object name, singular label, primary property, and required fields. FlitStack AI delivers a HubSpot-side schema plan for each custom object before writing data, so your HubSpot admin (or our team) creates the schema while data mapping is finalized. This adds one to three days to the planning phase depending on custom object count.

HubSpot API rate limits cap import throughput; large Panacea datasets may extend cutover timelines

HubSpot's private app API enforces rate limits per token, typically 100–120 requests per 10 seconds for bulk import operations. Panacea datasets exceeding 50,000 records may hit these limits during a full migration, extending clock time even when the logical migration is complete. FlitStack AI uses HubSpot's bulk import API where available and applies exponential backoff for throttled requests. For very large datasets, we schedule import batches across off-peak hours to maximize throughput. The delta-pickup window accounts for records modified during any extended import window.