Migrate from Panacea to Salesforce Sales Cloud

API pagination forces chunked extraction that extends timeline for high-volume Panacea datasets

Panacea's API-based data extraction uses pagination controls that require sequential API calls across offset pages for large record sets. High-volume Panacea instances (50,000+ records per object) may require multiple extraction passes to capture all pages. Each pass must be validated before loading into Salesforce, which extends planning time. FlitStack instruments the API pagination, tracks page boundaries per object, and validates record counts before each Bulk API load into Salesforce. This pagination overhead can add 1–3 days to the overall migration timeline for datasets exceeding 50,000 records per object.

Multi-company contact associations collapse to a single AccountId primary lookup

Panacea supports N:N contact-to-company associations natively, allowing a single contact to be linked to multiple companies simultaneously. Salesforce contacts have a single primary AccountId plus Account Contact Relationships for additional links. If a Panacea contact is associated with multiple companies, FlitStack maps the most-recently-modified association as the primary AccountId and creates Account Contact Relationships for the rest. Admins specify the tiebreaker rule (most recent, most active, or alphabetically first) during planning.

Salesforce field-level security requires post-migration grants per profile

When data loads via Bulk API, Salesforce field-level security (FLS) settings block access to fields where the running user profile lacks read or write permission. Custom fields created during schema setup will be invisible to profiles that haven't had FLS explicitly granted. FlitStack includes a FLS validation step in the sample migration diff and documents which fields need FLS grants per profile before the full run — this is a common cause of empty fields in Salesforce after migration if skipped.

N:N custom-object relationships need pre-created Salesforce junction objects

Panacea's flexible association model supports N:N links between custom objects without requiring an explicit junction entity. Salesforce requires a junction custom object with two master-detail or lookup relationships to replicate N:N associations. If your Panacea setup uses N:N custom-object relationships, the junction object schema must be created in Salesforce during the setup phase before data lands — this cannot be resolved after the migration runs without re-processing the affected records.

Salesforce daily API request limits require off-peak scheduling during cutover window

Salesforce Bulk API 2.0 is governed by a 24-hour rolling window for API requests — Enterprise Edition grants 100,000 daily requests plus 1,000 per user license. High-volume migration loads can approach this limit during the cutover window. FlitStack schedules bulk loads during off-peak hours (nights and weekends by default), monitors the daily rolling count, and ensures the delta-pickup window completes within the remaining allocation before the 24-hour window resets. If the limit is reached, subsequent loads are queued until the next rolling window, which can delay the delta-pickup completion.