products\/123<\/code><\/td>\nIn-app destination<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\nEach platform structures these components differently. The mapping challenge is converting between these structures while preserving all the information.<\/p>\n\n\n\n
Platform-Specific Link Formats<\/h2>\n\n\n\nFormat Type 1: Hash-Based Short Links<\/h3>\n\n\n\n Some platforms encode all link data in a short hash:<\/p>\n\n\n\n
https:\/\/platform.link\/AbCd123\n<\/code><\/pre>\n\n\n\nThe hash (AbCd123<\/code>) maps to a database record on the platform's servers. The actual deep link data (destination URL, campaign parameters, fallback behavior) is stored server-side and not visible in the URL.<\/p>\n\n\n\nMigration challenge:<\/strong> You cannot parse these URLs to extract the deep link data. You need to use the old platform's API to export the link configurations, then recreate them on the new platform.<\/p>\n\n\n\n\/\/ Export link data from hash-based links\nasync function exportShortLinks(oldPlatformApi) {\n const links = await oldPlatformApi.getLinks({ limit: 1000 });\n return links.map(link => ({\n shortUrl: link.url,\n deepLinkPath: link.deepLink,\n campaign: link.campaign,\n fallbackUrl: link.fallbackUrl,\n createdAt: link.createdAt,\n }));\n}\n<\/code><\/pre>\n\n\n\nFormat Type 2: Path-Based Links<\/h3>\n\n\n\n Some platforms encode the deep link destination in the URL path:<\/p>\n\n\n\n
https:\/\/links.yourapp.com\/products\/123\nhttps:\/\/links.yourapp.com\/profile\/user456\n<\/code><\/pre>\n\n\n\nThe path directly maps to the in-app destination. This format is the most URL-friendly and the easiest to migrate because the intent is visible in the URL itself.<\/p>\n\n\n\n
Migration strategy:<\/strong> Create the same routes on the new platform. If your custom domain stays the same, users never see a difference.<\/p>\n\n\n\nFormat Type 3: Query Parameter Links<\/h3>\n\n\n\n Some platforms pass deep link data as query parameters:<\/p>\n\n\n\n
https:\/\/platform.link\/open?link=https:\/\/yourapp.com\/products\/123&apn=com.yourapp.android&isi=123456789\n<\/code><\/pre>\n\n\n\n\n\n\nParameter<\/th>\n Purpose<\/th>\n<\/tr>\n<\/thead>\n \nlink<\/code><\/td>\nThe deep link destination<\/td>\n<\/tr>\n \napn<\/code><\/td>\nAndroid package name<\/td>\n<\/tr>\n \nisi<\/code><\/td>\niOS App Store ID<\/td>\n<\/tr>\n \nibi<\/code><\/td>\niOS bundle ID<\/td>\n<\/tr>\n \nefr<\/code><\/td>\nDisable interstitial page<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\nMigration challenge:<\/strong> The parameter names differ between platforms. You need a parameter mapping table.<\/p>\n\n\n\nFormat Type 4: Encoded JSON Links<\/h3>\n\n\n\n Some platforms encode link data as a base64 or JSON payload in the URL:<\/p>\n\n\n\n
https:\/\/platform.link\/open?data=eyJkZWVwX2xpbmsiOiJwcm9kdWN0cy8xMjMiLCJjYW1wYWlnbiI6InN1bW1lcl9zYWxlIn0=\n<\/code><\/pre>\n\n\n\nMigration challenge:<\/strong> You need to decode the payload to extract link data, then re-encode it in the new platform's format.<\/p>\n\n\n\nBuilding a Link Mapping Table<\/h2>\n\n\n\n For each link you need to migrate, create a mapping entry:<\/p>\n\n\n\n
\/\/ Link mapping entry\nconst linkMapping = {\n oldUrl: 'https:\/\/old-platform.link\/AbCd123',\n oldFormat: {\n deepLink: 'products\/123',\n campaign: 'summer_sale',\n source: 'email',\n medium: 'newsletter',\n fallbackUrl: 'https:\/\/yourapp.com\/products\/123',\n iosAppStoreId: '123456789',\n androidPackage: 'com.yourapp.android',\n },\n newUrl: 'https:\/\/links.yourapp.com\/products\/123',\n newFormat: {\n route: '\/products\/:id',\n params: { id: '123' },\n campaign: 'summer_sale',\n source: 'email',\n medium: 'newsletter',\n fallbackUrl: 'https:\/\/yourapp.com\/products\/123',\n },\n};\n<\/code><\/pre>\n\n\n\nBulk Export from Old Platform<\/h3>\n\n\n\n Most platforms provide an API for bulk link export:<\/p>\n\n\n\n
async function exportAllLinks(oldPlatformApi) {\n let page = 1;\n const allLinks = [];\n\n while (true) {\n const response = await oldPlatformApi.getLinks({\n page,\n limit: 100,\n orderBy: 'clicks',\n direction: 'desc',\n });\n\n if (response.links.length === 0) break;\n allLinks.push(...response.links);\n page++;\n }\n\n return allLinks;\n}\n<\/code><\/pre>\n\n\n\nExport links ordered by click count (descending). Migrate the highest-traffic links first.<\/p>\n\n\n\n
Route Mapping Patterns<\/h2>\n\n\n\nDirect Path Mapping<\/h3>\n\n\n\n The simplest case: the path structure is identical on both platforms.<\/p>\n\n\n\n
Old: https:\/\/links.yourapp.com\/products\/123\nNew: https:\/\/links.yourapp.com\/products\/123\n<\/code><\/pre>\n\n\n\nNo conversion needed. Configure the same routes on the new platform.<\/p>\n\n\n\n
Path Transformation<\/h3>\n\n\n\n The path structure changes between platforms:<\/p>\n\n\n\n
Old: https:\/\/old.link\/open\/products?id=123\nNew: https:\/\/links.yourapp.com\/products\/123\n<\/code><\/pre>\n\n\n\nCreate a mapping function:<\/p>\n\n\n\n
function mapPath(oldPath, oldQuery) {\n \/\/ Old format: \/open\/products?id=123\n \/\/ New format: \/products\/123\n if (oldPath.startsWith('\/open\/')) {\n const resource = oldPath.replace('\/open\/', '');\n const id = oldQuery.id;\n return `\/${resource}\/${id}`;\n }\n return oldPath;\n}\n<\/code><\/pre>\n\n\n\nWildcard Routes<\/h3>\n\n\n\n If the old platform uses specific link IDs but your new platform uses path-based routes, set up a wildcard redirect:<\/p>\n\n\n\n
Old: https:\/\/old.link\/xK3mP \u2192 resolves to products\/123\nOld: https:\/\/old.link\/yN7qR \u2192 resolves to profile\/user456\n\nNew: https:\/\/links.yourapp.com\/products\/:id\nNew: https:\/\/links.yourapp.com\/profile\/:userId\n<\/code><\/pre>\n\n\n\nYou cannot set up wildcard redirects for hash-based short links. Each one needs an individual redirect entry or a redirect service that maps old hashes to new URLs.<\/p>\n\n\n\n
Campaign Parameter Mapping<\/h2>\n\n\n\n Different platforms use different parameter names for the same concepts:<\/p>\n\n\n\n\n\n\nConcept<\/th>\n Platform A<\/th>\n Platform B<\/th>\n Platform C<\/th>\n Tolinku<\/th>\n<\/tr>\n<\/thead>\n \nCampaign name<\/td>\n campaign<\/code><\/td>\n~campaign<\/code><\/td>\nc<\/code><\/td>\ncampaign<\/code><\/td>\n<\/tr>\n\nTraffic source<\/td>\n source<\/code><\/td>\n~channel<\/code><\/td>\npid<\/code><\/td>\nsource<\/code><\/td>\n<\/tr>\n\nMedium<\/td>\n medium<\/code><\/td>\n~feature<\/code><\/td>\naf_adset<\/code><\/td>\nmedium<\/code><\/td>\n<\/tr>\n\nAd creative<\/td>\n ad<\/code><\/td>\n~ad_name<\/code><\/td>\naf_ad<\/code><\/td>\nad<\/code><\/td>\n<\/tr>\n\nCustom data 1<\/td>\n data<\/code><\/td>\n~tags<\/code><\/td>\naf_sub1<\/code><\/td>\ncustom<\/code><\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\nConversion Script<\/h3>\n\n\n\n Write a script that converts parameter names:<\/p>\n\n\n\n
function mapCampaignParams(oldParams, platformType) {\n const mapping = {\n platformA: {\n campaign: 'campaign',\n source: 'source',\n medium: 'medium',\n },\n platformB: {\n '~campaign': 'campaign',\n '~channel': 'source',\n '~feature': 'medium',\n },\n platformC: {\n c: 'campaign',\n pid: 'source',\n af_adset: 'medium',\n },\n };\n\n const map = mapping[platformType];\n const newParams = {};\n\n for (const [oldKey, value] of Object.entries(oldParams)) {\n const newKey = map[oldKey] || oldKey;\n newParams[newKey] = value;\n }\n\n return newParams;\n}\n<\/code><\/pre>\n\n\n\nRedirect Strategy for Old Links<\/h2>\n\n\n\n After mapping link formats, you need to redirect old links to their new equivalents.<\/p>\n\n\n\n
Individual Redirects<\/h3>\n\n\n\n For high-traffic links, set up individual 301 redirects:<\/p>\n\n\n\n
\/\/ Generate redirect rules from mapping table\nfunction generateRedirects(mappings) {\n return mappings.map(m => ({\n source: new URL(m.oldUrl).pathname,\n destination: m.newUrl,\n statusCode: 301,\n }));\n}\n<\/code><\/pre>\n\n\n\nPattern-Based Redirects<\/h3>\n\n\n\n If the path structure follows a consistent pattern, use regex-based redirects:<\/p>\n\n\n\n
# Nginx: redirect old format to new format\nrewrite ^\/open\/(.+)\\?id=(.+)$ \/$1\/$2 permanent;\n<\/code><\/pre>\n\n\n\nRedirect Service<\/h3>\n\n\n\n For large-scale migrations with thousands of hash-based short links, consider a lightweight redirect service:<\/p>\n\n\n\n
\/\/ Simple redirect service\nimport express from 'express';\n\nconst app = express();\nconst redirectMap = loadRedirectMap(); \/\/ Load from database or JSON\n\napp.get('\/:hash', (req, res) => {\n const newUrl = redirectMap.get(req.params.hash);\n if (newUrl) {\n res.redirect(301, newUrl);\n } else {\n \/\/ Fallback: redirect to app homepage\n res.redirect(302, 'https:\/\/yourapp.com');\n }\n});\n<\/code><\/pre>\n\n\n\nThis service runs on the old domain and redirects to the new platform's URLs.<\/p>\n\n\n\n
Validation<\/h2>\n\n\n\n After mapping and configuring redirects, validate:<\/p>\n\n\n\n