Switching from InDesign to DesignCraft: a practical migration checklist.
The move is less about installing an app and more about your files, your muscle memory and your print partners. Here is the checklist, in the order that loses the least work.
DesignCraft is an open-source page layout and publishing workspace in the ArtCraft family — a native app for macOS, Windows and Linux for arranging pages, typography and publication-ready compositions, where you set the frame, place type and images, and refine the rhythm of a publication. If you are moving from an InDesign subscription, the move is plausible only after your files, handoffs and habits survive a test. This checklist turns it into a safe, testable process.
The short answer
quotable summarySwitch by testing, not by believing. Because DesignCraft's documented sources do not enumerate an InDesign file importer, treat format compatibility as the first gate: check the official product page and release notes for current import and export behavior, then run two weeks of real work in parallel before letting the subscription lapse. Keep original files untouched, keep delivering in the format your client and print partner expect, and treat InDesign as the reference implementation until your own files prove otherwise.
Before you install anything: the inventory
Write down the answers first — the whole migration is judged against this list.
- The formats you receive and deliver. InDesign-centric work moves as INDD documents, with IDML and PDF as common interchange. Note every format endpoint your clients, collaborators and print vendors require.
- The features you actually touch weekly. DesignCraft's documented surface covers setting the frame, placing type and images, and refining the rhythm of a publication. Anything beyond it — template libraries, automation, ecosystem-dependent tricks — goes on the "will not transfer by default" list.
- The handoffs that pay you. Which files go to whom, in which format, and who has to reopen them. Print vendors are the strictest audience in publishing.
- Your ecosystem dependencies. Templates, styles, scripts, team libraries. List them by name. Ecosystem assets do not travel between tools; know what you are leaving before you leave it.
Moving your files
The format gate comes first: this guide's sources do not document an InDesign file importer for DesignCraft, so check the official page and current release notes for what the app imports and exports today before planning any conversion. Whatever the answer, the discipline that keeps you safe stays the same:
1. Copy, never move. Your InDesign-era originals stay exactly where they are, read-only, for at least one full billing cycle after the switch.
2. Test five documents before trusting fifty: your heaviest long document, a style-heavy template, a client-received file, an uncommon-font layout, and the most complex publication you own.
3. Inspect structure by structure, not by thumbnail. Check that the frame system holds, type keeps its hierarchy and its fonts — substitutions are the classic silent failure — and every placed image sits where it should.
4. Round-trip once. Export from DesignCraft, reopen the result in whichever tool your collaborator or print partner actually uses, and compare. This single test predicts most real-world surprises.
5. Note anything that degrades and decide its fate: rebuild it in DesignCraft's terms, keep that one job in InDesign, or restructure the work so the fragile element disappears.
Rebuilding muscle memory
The honest part of a switch: the first week feels slower, and no comparison page can fix that. DesignCraft's documented workflow — set the frame, place type and images, refine the rhythm — maps to the core of any layout practice, but menu placements, dialog layouts and defaults are its own. Two habits shorten the ramp:
First, relearn by task, not by toolbar: for one real job, find each step's new home — frame, type, image, export — instead of touring every menu. Second, keep notes on anything that took longer than it should; after a week they become your personal shortcut sheet, and the ramp is over. The ArtCraft Discord and the repository issue tracker are the right places to ask when a step has no obvious new home.
The two-week parallel plan
| Days | What you run | What proves it works |
|---|---|---|
| 1–2 | Install the current build for your platform from the repository, read the release notes, and check the format gate: what your five test documents do when you bring them in. | A written list of what opened, what imported, and what has to be rebuilt from source material. |
| 3–5 | Lay out one small, low-stakes real job entirely in DesignCraft: set the frame, place type and images, refine the rhythm. | The exported result reopens where it must; nothing needed a rescue trip back to InDesign. |
| 6–9 | Run your normal jobs in both tools: draft in DesignCraft, keep InDesign as the reference. Compare time and result quality per task. | Per-task notes: where DesignCraft matched, where it fell short, where it was genuinely fine. |
| 10–13 | Move the real handoffs: deliver actual client and print files from DesignCraft, after verifying each result reopens or prints correctly on the receiving end. | Zero handoff failures across a full delivery cycle. |
| 14 | Decision point: migrate fully, stay hybrid, or stay on InDesign. All three are legitimate outcomes of an honest test. | Your inventory list from day zero, answered line by line. |
Scope note: the plan is a testing schedule, not a claim about DesignCraft's capabilities beyond its documented feature list. Your own files are the evidence.
Working with clients during and after the switch
Nothing about your side of a tool change obliges you to change the deliverable — keep exchanging files in the formats your clients and print partners already expect. Tell collaborators what changed on your side, and keep the original files untouched so any dispute can be re-verified in the reference tool. If a client's workflow hard-depends on InDesign-specific behaviors you cannot honor, that job stays in InDesign or that conversation happens early. The switch is yours; the contract is shared.
Evidence and editorial method
checked 2026-10-21Who wrote this: DesignCraft Fan Guide editors, independent and unaffiliated with ArtCraft or Adobe. How: capability claims come from the official DesignCraft product page and public repository; the migration method is standard editorial practice for tool switches, expressed as tests you run rather than numbers we invent.
What to verify yourself: current import and export behavior before installing, the behavior of your own layout files, and the terms of your Adobe subscription before cancelling anything.
Questions readers ask
Will my INDD files open in DesignCraft?
Our documented sources do not enumerate a native InDesign file importer, so treat this as the first question to verify, not a promise: check the official product page and the current release notes for import and export behavior, and test with real files from your own archive before migrating anything important.
Should I cancel my InDesign subscription on day one?
No. Run both tools through a test period — we suggest two weeks on real work — and cancel only when your documents, handoffs and print workflows have all been checked. Subscription plans usually renew monthly, so a short overlap is cheap insurance.
How do I keep working with clients during the switch?
Keep delivering in the format each client and print partner already expects, keep the original files untouched, and verify every exported result reopens correctly on the receiving end. Tell collaborators what changed on your side and keep one tool as the reference while you test.
What this article does not claim
It does not claim that InDesign documents transfer at all, that DesignCraft covers InDesign's full feature surface, or that any specific schedule suits every workload. It publishes no benchmarks and no prices. It is an editorial checklist from a fan-made guide; the official sources remain the authority.