Board migration drops card aging colors when destination workspace lacks Power-up

Resolution

To retain card aging visual indicators, the Card Aging Power-up must be enabled on the destination board. Because the visual cues (color shifts and fading) are rendered dynamically by the Power-up based on each card's dateLastActivity timestamp, the colors will reappear as soon as the Power-up is activated, provided the migration method preserved the original activity metadata.

Likely Explanation vs. Confirmed Behavior

The visual appearance of an "aged" card is not a stored attribute of the card itself, but a client-side render triggered by the Power-up.

• Confirmed: The Card Aging Power-up reads the dateLastActivity field to determine which visual style to apply.
• Confirmed: Enabling the Power-up after a migration will restore visuals if the underlying timestamps remain intact.
• Uncertainty: Whether dateLastActivity is preserved depends entirely on the migration method. Native Trello board copying typically preserves metadata, but custom API scripts that recreate cards from scratch may reset the activity date to the moment of creation, effectively "resetting" the age of all cards.

Recommended Migration Sequence

For a zero-downtime migration that prevents visual loss, use the following sequence:

1. Pre-enable Power-up: Enable the Card Aging Power-up on the destination board before importing data. This ensures visuals are active the moment cards arrive.
2. Execute Migration: Perform the board copy or import. If using a custom script, implement exponential backoff for HTTP 429 (Too Many Requests) responses, as Trello's rate limits vary by token and account type.
3. Verify Metadata: Check a sample of cards via the API to ensure the activity date was not reset during the move:

   GET /1/cards/{id}?fields=dateLastActivity

4. Cutover: Switch users to the new workspace once visual verification is complete.

Diagnostic Requirement

To determine if your specific migration will reset card ages, please specify the migration method being used (e.g., native "Copy Board" feature, a third-party tool, or a custom API script).