Improve transition from Unsubscribe Link 3 to 4.

Open

#89 opened on Mar 4, 2025 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 28/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Domain: backend, database, documentation

Research direction

Start by installing both version 3 and version 4 apps and creating sample version 3 data, as outlined in the sprint tasks. Investigate the proposed flow for moving data between the different API names and whether it can be included in a managed or unmanaged package. Done means a tested transition path and documentation suitable for publication on the proposed blog or commons site.

Written by the indexing model from the issue text.

Description

enhancement help wanted

What does someone need to do if they have Unsubscribe Link 3 (currently on appExchange) and want to transition to version 4 without losing their data? The objects all have different API names.
One suggestion is that they install version 4 (the managed package) then run a flow to move all data to the new objects. Then uninstall version 3.
Tasks for sprint:

Install both apps. (I don't think the sites need to be set up for this this to work).
Create sample data in version 3.
Create a flow that will move the data to the new app. Pull it into the repo or make it into an unmanaged package.
Write documentation on the transition that will be posted on Jessie's blog or the commons blog or somewhere appropriate.
Can the flow be included in the managed package? I don't think so because not everyone will already have version 3, so the flow would reference fields they don't have.

Dominant language: Apex
Stars: 7
Forks: 21
Avg merge: 1d 19h
Merged PRs (30d): 1

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] [Connector-V2] [Http] A streaming Http source never completes a checkpoint: poll_interval_millis is waited out holding the checkpoint lock Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

apache/seatunnel#12411 · Opened Sep 20, 2026
wafv2: TagResource/UntagResource don't enforce the 50-tag limit or key/value length limits Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

floci-io/floci#4035 · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
popularity.exclude_admin does not work for admin2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

getgrav/grav-plugin-api#45 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026

More Backend & API Design issues